[swift-evolution] Some concerns on custom operators
rjmccall at apple.com
Sun Nov 27 20:01:27 CST 2016
> On Nov 26, 2016, at 3:19 PM, Robert Widmann <devteam.codafi at gmail.com> wrote:
> Just gotta field a version of that proposal that doesn’t “look like Haskell” :)
> Seriously, though, would there be any objection to restoring the old behavior of just silently ignoring perfect duplicates of operator definitions across frameworks sans proposal?
The definition of "perfect duplicates" is more complex now. It would be easy to ignore duplicates that name the same precedencegroup, but that's probably not what's happening here.
>> On Nov 10, 2016, at 10:54 AM, Joe Groff <jgroff at apple.com> wrote:
>>> On Nov 10, 2016, at 7:23 AM, Jay Abbott via swift-evolution <swift-evolution at swift.org> wrote:
>>> Would it make sense to allow some kind of operator aliasing on import, so that developers can at least work-around library conflicts?
>> Definitely. I think something like the import improvements Robert Widmann was proposing a while back are sorely needed, not only for operators but for managing conflicts in general.
More information about the swift-evolution