[swift-evolution] Some concerns on custom operators
dabrahams at apple.com
Sat Nov 26 22:02:16 CST 2016
on Sat Nov 26 2016, David Sweeris <davesweeris-AT-mac.com> wrote:
>> On Nov 26, 2016, at 17:19, Robert Widmann via swift-evolution <swift-evolution at swift.org> wrote:
>> Just gotta field a version of that proposal that doesn’t “look like Haskell” :)
> Is there something wrong with Haskell's approach to imports? I don't
> know how they do it, so I'm unaware of any pros/cons to their
> approach. The ":)" makes me think I'm missing something...
>> 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?
> Yeah, it could silently change how statements get evaluated, if I
> start writing code using one library's operators, then import a 3rd
> library which defines the same operators but with different
differnt precedences => not perfect duplicates, right?
More information about the swift-evolution