Actually I don’t like the prioritization of the modules import. I’m much more in favor of disambiguating at call site. like we have to do in any other case of ambiguity in Swift. The concept of precedence is only present in operators and that makes sense because it’s in their nature. I think #4 or #5 or any other way to disambiguate at call site would be the most appropriate.
> On Jun 4, 2016, at 10:29 PM, Paulo Faria <[email protected]> wrote: > > Hello, everyone. > > I want to discuss the problem of name ambiguity when a computed property or > function is defined with the same name and type in different modules. > Currently there’s no way to disambiguate the implementation in use cases > similar to the one contained in the gist below. > > https://gist.github.com/paulofaria/f48d0b847a0fb7c125d163d0e349500a > <https://gist.github.com/paulofaria/f48d0b847a0fb7c125d163d0e349500a> > > The gist also contains some informal proposals. The idea is to create a > formal proposal based on the discussion that shall follow. > > Cheers, > Paulo
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
