Just to raise awareness that using this kind of imports can difficult for readability, that maybe it should not be removed from the language but discourage by the community.
Just following the python example, from PEP8 the python style guides: "Wildcard imports ( from <module> import * ) should be avoided, as they make it unclear which names are present in the namespace, confusing both readers and many automated tools. There is one defensible use case for a wildcard import, which is to republish an internal interface as part of a public API (for example, overwriting a pure Python implementation of an interface with the definitions from an optional accelerator module and exactly which definitions will be overwritten isn't known in advance)." Also, depending on an IDE or external tools for me it's a sign that there is a problem. As others have said, what about github and who's going to maintain the plugins for all the IDEs, maybe one day you'll be through ssh with the system's default vim. It's just my perspective, cheers. On Tue, Nov 15, 2016 at 7:55 PM, Joey Eremondi <joey.eremo...@gmail.com> wrote: > I'm not sure what your proposing, the Python syntax you stated does the > exact same thing as exposing (..). > > Showing where a name came from would be a great IDE feature though, > Haskell can do this on Atom and it's really helpful. > > On Nov 15, 2016 10:33 AM, "Alejandro Do Nascimento" < > alejandro...@gmail.com> wrote: > >> I'm just starting with Elm, I'm as newbie as someone can be. I'm reading >> some examples of how to use the hop router on github, most of the things >> I've have found use a lot of *exposing (..)* so I find myself wasting >> time just searching the declarations of the symbols I encounter. I think >> that's the only thing that I have found that makes Elm program a little >> harder to read. >> >> Maybe you can do like python does, in python you can import everything >> into your namespace with *from module import ** but that's something >> that's kind of frown upon the community and official style guide. >> On Monday, August 22, 2016 at 5:56:24 PM UTC+2, Francesco Orsenigo wrote: >>> >>> Are you going to write such plugin for every possible editor? >>> Is every newbie going to have such plugin? >>> What about browsing code from GitHub? >>> >>> A language's readability should not depend on tooling. >>> >>> On Mon, Aug 22, 2016 at 5:52 PM, William Bailey <bi...@deepfinesse.com> >>> wrote: >>> > For years I coded in Java using IntelliJ. It was super easy in that >>> IDE to >>> > hover on any symbol, system or otherwise, and learn all about it. Or >>> hit >>> > ctrl-B (eg) to drill into the source. Again, worked fine for system >>> > libraries and was really useful for seeing how the under-the-covers >>> stuff >>> > worked. >>> > >>> > When I started coding in go-lang a couple years ago, people were >>> griping >>> > about having to manually remove unused imports as the compiler would >>> not >>> > allow that. But now, most editors have plug-ins that do that >>> automatically. >>> > >>> > So... I think focusing on what the core language should and should not >>> allow >>> > here is misguided. Just need better IDE tools. >>> > >>> > -- >>> > You received this message because you are subscribed to a topic in the >>> > Google Groups "Elm Discuss" group. >>> > To unsubscribe from this topic, visit >>> > https://groups.google.com/d/topic/elm-discuss/ydhKsvJtDZw/unsubscribe. >>> >>> > To unsubscribe from this group and all its topics, send an email to >>> > elm-discuss...@googlegroups.com. >>> > For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elm-discuss+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/elm-discuss/ydhKsvJtDZw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- AD.N -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
