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

[Austin Zheng]

'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.

Best,
Austin

On Tue, Mar 8, 2016 at 1:48 PM, Erica Sadun <erica at ericasadun.com> wrote:

> cite The Swift Programming Language (Swift 2.2)
>
> http://imgur.com/sFPhPxz
>
> -- E
>
>
> On Mar 8, 2016, at 2:42 PM, Charles Kissinger via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>
> On Mar 8, 2016, at 12:33 PM, Austin Zheng via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> I agree that operator syntax needs to be reworked, but I prefer that
> whatever proposal ends up being accepted not abuse the word 'fixity' to
> mean something it doesn’t.
>
>
> I can’t say with certainty whether “fixity” is cromulent or incromulent
> ;-), but how about: “position” or “placement”?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160308/827002ed/attachment.html>