[swift-evolution] [Draft] Resolving operator precedence conflicts

Erica Sadun erica at ericasadun.com
Wed Mar 9 13:12:19 CST 2016

> On Mar 9, 2016, at 12:10 PM, Charles Kissinger <crk at akkyra.com> wrote:
>> On Mar 8, 2016, at 1:52 PM, Austin Zheng <austinzheng at gmail.com <mailto:austinzheng at gmail.com>> wrote:
>> 'Fixity' already has a non-technical meaning ("the state of being unchanged and permanent"), and an unrelated technical one (a synonym for associativity; search "assocativity fixity operator" for examples). If we're using it in this different way, I respectfully submit that we should reconsider.
> You are correct, of course, but a subset of computer scientists have been abusing the term in this way for at least a couple of decades. Their novel usage of “fixity” now has a degree of fixity, so it may be too late to fix "fixity".

It's become a termity of art.

-- E

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160309/711d9fb2/attachment.html>

More information about the swift-evolution mailing list