I've searched for "import exposing (..)" but I couldn't find the thread. I'll carry on with import exposing (..), but I'll be sure (i.e. I'll have to remember!) to post back here if I encounter a problem.
On Thursday, August 18, 2016 at 4:18:56 PM UTC+1, Janis Voigtländer wrote: > > I can’t search for the thread right now, but I’m sure you can find it > yourself via the archive. In any case, one aspect of it (but I think there > were more) was this: https://github.com/elm-lang/elm-make/issues/61 > > > 2016-08-18 17:08 GMT+02:00 Will White <[email protected] <javascript:>>: > >> What unexpected results? The compiler has your back if two unqualified >> functions have the same name. >> >> On Thursday, August 18, 2016 at 3:56:50 PM UTC+1, Janis Voigtländer wrote: >>> >>> That's not an answer to my question I understand as a problem >>> description. >>> >>> Also, there have been earlier threads here that have discussed what can >>> go wrong if you unwittingly import with exposing everything. So, where not >>> remembering that one of those imports brought a certain function name into >>> scope, lead to unexpected results. If your concern is valid, theirs is at >>> least as much. >>> >>> Am 18.08.2016 um 17:48 schrieb Will White <[email protected]>: >>> >>> You have to remember to qualify. >>> >>> On Thursday, August 18, 2016 at 3:40:21 PM UTC+1, Janis Voigtländer >>> wrote: >>>> >>>> In what ways are qualified imports at odds with safe code? >>>> >>>> I think the opposite is the case: unqualified imports lead to less code >>>> safety. >>>> >>>> Am 18.08.2016 um 17:37 schrieb Will White <[email protected]>: >>>> >>>> I prefer safe code to qualified imports. >>>> >>>> On Thursday, August 18, 2016 at 3:11:21 PM UTC+1, Peter Damoc wrote: >>>>> >>>>> "Qualified imports are preferred." >>>>> >>>>> http://elm-lang.org/docs/syntax#modules >>>>> >>>>> I try to avoid as much as possible importing everything from a module. >>>>> If I would have IDE support for automatic imports I would never do a >>>>> import >>>>> Module exposing (..). >>>>> >>>>> -- >>>> 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 [email protected]. >>>> 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 [email protected]. >>> 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 [email protected] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
