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? > On Nov 10, 2016, at 10:54 AM, Joe Groff <jgr...@apple.com> wrote: > > >> On Nov 10, 2016, at 7:23 AM, Jay Abbott via swift-evolution >> <swift-evolution@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. > > -Joe _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
