Just to be clear, in 1. I did `toString Integer`, expecting that to call elm-integer's toString, not Basic.toString. In the first bullet point, I meant to say "...even though `toString Integer` is valid...".
On Wednesday, July 20, 2016 at 3:04:23 PM UTC+1, Will White wrote: > > Coming from https://github.com/elm-lang/error-message-catalog/issues/135, > I'd like to know what you think we could do about ambiguous uses of e.g. > `toString`. For instance: > > > 1. I was using elm-integer, which has its own `toString` function for > its massive integers, and I called it on an elm-integer Integer. > 2. My code *actually* called `Basics.toString` on the Integer, so the > result was not as expected. Luckily I caught it. > > I can think of two ways to handle there being more than one toString > around: > > > - Warn the developer that the use of `toString` is ambiguous, even > though `Basics.toString Integer` *is* valid (Basics.toString changes > *any* type to a String). Namespacing the toString would make the > warning go away. > - Call the toString that's in the same module as the type of the > argument is in, i.e. the toString that's in the same module as Integer. > > I'm sure this will affect other functions as well as `toString`. > -- 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.
