<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 1:48 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">As Anton mentioned earlier, I feel the same way with respect to naming. No need to reiterate the points already made, but I do want to chime in on the topic of rarely used syntax.<br class=""><br class="">While I agree of course that a cumbersome syntax for a rarely used feature is _not as bad_ as a cumbersome syntax for a common feature, all other things being equal, I think we should press for the most elegant possible syntax for all aspects of the language. It is needless, IMO, to insist that less commonly used features *ought* to be weighed down with more cumbersome spelling.<br class=""></div></blockquote><div><br class=""></div><div>I agree. I’m not arguing against elegant syntax here. In fact the opposite - my preference is for the syntax I consider to be the most elegant (above and below in this case). I’m just not willing to argue to strenuously over a less commonly used feature when the alternatives are reasonable, if slightly less elegant.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="">On Thu, Jun 30, 2016 at 13:25 Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
<br class="">
Sent from my iPad<br class="">
<br class="">
On Jun 30, 2016, at 1:08 PM, John McCall via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
<br class="">
>> On Jun 30, 2016, at 2:34 AM, Anton Zhilin via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>> <a href="https://github.com/apple/swift-evolution/blob/master/proposals" rel="noreferrer" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/proposals</a><br class="">
>> /<a href="http://0077-operator-precedence.md/" rel="noreferrer" target="_blank" class="">0077-operator-precedence.md</a><br class="">
>><br class="">
>> Idea #1<br class="">
>><br class="">
>> There is a high chance that 'higherThan'/'lowerThan' names will be<br class="">
>> chosen. I still see a problem with that. Keywords in Swift are written<br class="">
>> in full lowercase, so we should actually take 'higherthan'/'lowerthan'.<br class="">
>><br class="">
>> But then what's the point of the preposition? It blends with<br class="">
>> higher/lower and doesn't actually add any clarity. So we should drop<br class="">
>> 'than' and have just higher/lower or above/below or succeeds/preceeds or<br class="">
>> whatever we choose, but *in a single word*.<br class="">
><br class="">
> The preposition does add clarity. Are the listed precedences the ones that are<br class="">
> higher than the current precedence, or are they the ones that the current<br class="">
> precedence is higher than?<br class="">
<br class="">
I agree with that for higher and lower, but I think above and below are pretty clear (in the example just below it seems very clear (to me at least) that Multiplicative is above additive and below Exponentiative).<br class="">
<br class="">
I think above and below are aesthetically the best here, but as has been noted this will be a rarely used feature so I won't feel bad if something else is selected,<br class="">
<br class="">
<br class="">
><br class="">
> John.<br class="">
><br class="">
>><br class="">
>> Idea #2<br class="">
>><br class="">
>> I personally don't like the direction in which the proposal moved (I<br class="">
>> understand the reasons). Before the first review, consensus seemed to be<br class="">
>> on this:<br class="">
>><br class="">
>> precedence Multiplicative {<br class="">
>> above Additive<br class="">
>> below Exponentiative<br class="">
>> }<br class="">
>><br class="">
>> And now:<br class="">
>><br class="">
>> precedencegroup MultiplicativePrecedence {<br class="">
>> higherThan: AdditivePrecedence<br class="">
>> lowerThan: ExponentiativePrecedence<br class="">
>> }<br class="">
>><br class="">
>> Don't you have a feeling that something cute and 'swift' was turned into<br class="">
>> a monster?<br class="">
>><br class="">
>> At least, if we change keywords, we will get this:<br class="">
>><br class="">
>> precedence MultiplicativePrecedence {<br class="">
>> above: AdditivePrecedence<br class="">
>> below: ExponentiativePrecedence<br class="">
>> }<br class="">
>><br class="">
>> I also like in above/below that they are written with the same number of<br class="">
>> letters, meaning that they will line up nicely.<br class="">
>><br class="">
>> _______________________________________________<br class="">
>> swift-evolution mailing list<br class="">
>> <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
><br class="">
> _______________________________________________<br class="">
> swift-evolution mailing list<br class="">
> <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div>
</div></blockquote></div><br class=""></body></html>