> On Mar 16, 2017, at 8:27 PM, Slava Pestov via swift-evolution > <[email protected]> wrote: > > Overload resolution has a lot of heuristics, but it’s not magic. It simply > doesn’t know how to handle this case. > > I’d be in favor of consolidating and simplifying the overload resolution > rules, with the goal of disambiguating common cases that are currently > ambiguous. We might even be able to do that without breaking too much user > code, since a lot of the rules there were put in place to handle specific > situations that came up in the standard library. > > However adding more heuristics to handle specific examples is a -1 from me. > :-)
There is a general guideline that more specific things should be favored over less specific ones, which I'm surprised isn't applying here. (I agree we should have real *rules* of course.) -Joe _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
