Not at all. You'd use qualified imports. `import Html exposing (div, span, text, input, form)`
or `import Html as H` and then `H.div` `H.text` and so on. One of the strength of Elm is keeping everything very explicit, which makes it super newbie friendly. On Mon, Aug 22, 2016 at 3:08 PM, Will White <will.n.wh...@gmail.com> wrote: > I don't think it should be disallowed entirely. Disallowing it would make > Html and other familiar things like that harder to read, without helping > understanding. > > On Monday, August 22, 2016 at 11:10:38 AM UTC+1, Francesco Orsenigo wrote: >> >> The only issue I have with imports is that any code that contains several >> unqualified imports is a pain in the ass to learn. >> >> Example: >> https://github.com/Bogdanp/elm-combine/blob/2.2.1/examples/Python.elm >> >> As a newbie, it's immensely frustrating being unable to easily track which >> of the `import Whatever exposing (..)` is actually providing a specific >> symbol. >> It should be disallowed entirely. >> I don't mind writing more if it makes my code more readable. > > -- > 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. -- 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.
