On painting the relative-precedence bikeshed, I would lean slightly toward “before” and “after”. They are short, single words with unambiguous meaning.<div><br></div><div>Moreover, the actual point of interest is “Which operators will be evaluated before which other ones?”<br><br>Plus the word “precedence” itself connotes the idea of one thing preceding another, which is exactly what “before” and “after” convey.</div><div><br></div><div>It is true that we often talk about things having “higher” precedence, but in context that becomes “higherThan”, which is lengthy.</div><div><br></div><div>Now “above” / “below” would work just fine, though to me at least it isn’t as immediately-self-evident which is which for operators, as it would be with “before” / “after”.</div><div><br></div><div>Another option would be “aheadOf” / “behind”, which seem clear in meaning but mismatched in word-count.</div><div><br></div><div>Actually, I think “precedes” / “follows” might be worth considering. The former would be more common and it exactly matches not only the semantic but the exact terminology we want. Maybe “follows” isn’t maximally ideal, but at least it doesn’t have a synonym problem like “succeeds” does.</div><div><br></div><div>Even there though, an ambiguity exists between “the group being defined precedes the listed one” and “the listed group precedes the one being defined”.</div><div><br></div><div>So I would still tend toward prepositional descriptors, especially “before” and “after”.</div><br><div>Nevin<br><br>On Friday, July 1, 2016, Anton Zhilin via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">John McCall via swift-evolution <swift-evolution@...> writes:<br>
<br>
> > There is a high chance that 'higherThan'/'lowerThan' names will be<br>
> > chosen. I still see a problem with that. Keywords in Swift are<br>
written<br>
> > in full lowercase, so we should actually take<br>
'higherthan'/'lowerthan'.<br>
> ><br>
> > But then what's the point of the preposition? It blends with<br>
> > higher/lower and doesn't actually add any clarity. So we should drop<br>
> > 'than' and have just higher/lower or above/below or<br>
succeeds/preceeds or<br>
> > whatever we choose, but *in a single word*.<br>
><br>
> The preposition does add clarity. Are the listed precedences the ones<br>
that are<br>
> higher than the current precedence, or are they the ones that the<br>
current<br>
> precedence is higher than?<br>
><br>
> John.<br>
<br>
I meant that following keywords should be preferred to be written in all<br>
lowercase. But in our case, we lose clarity from doing so.<br>
<br>
An elegant solution seems to be to find expressive single-word keywords<br>
for our purpose, their advantage is that they can strictly follow<br>
keyword naming rules without losing clarity.<br>
<br>
It seems that mine and some other people' concerns are based on this<br>
naming inconsistency of higherThan and lowerThan. There are plenty of<br>
other good options: above/below, before/after, precedes/succeeds.<br>
<br>
I know your opinion, but anyways want this argument to be risen during<br>
internal discussion.<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>