<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 7, 2016 at 11:28 AM, Dmitri Gribenko via swift-evolution <span dir="ltr">&lt;<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Thu, Jul 7, 2016 at 9:27 AM, John McCall &lt;<a href="mailto:rjmccall@apple.com">rjmccall@apple.com</a>&gt; wrote:<br>
&gt; On Jul 7, 2016, at 9:23 AM, Dmitri Gribenko via swift-evolution<br>
&gt; &lt;<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>&gt; wrote:<br>
&gt;&gt; Proposal link:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0077-operator-precedence.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0077-operator-precedence.md</a><br>
&gt;<br>
&gt; Dave, Max and I discussed SE-0077 and reviewed the names of precedence<br>
&gt; groups.<br>
&gt; Here&#39;s our recommendation.<br>
&gt;<br>
&gt; In general, we think some names don&#39;t read well and have some ambiguities,<br>
&gt; for<br>
&gt; example, &quot;LogicalAndPrecedence&quot; (looks like a conjunction),<br>
&gt; &quot;AdditivePrecedence&quot; (&quot;additive&quot; is an adjective that modifies<br>
&gt; &quot;precedence&quot;),<br>
&gt; &quot;RangePrecedence&quot; (&quot;range&quot; is not an adjective, stands out).<br>
&gt;<br>
&gt; We think that two directions would be fruitful:<br>
&gt;<br>
&gt; 1.  If the names of precedence groups will be in the same namespace as<br>
&gt; types,<br>
&gt;     then we recommend pushing the names of precedence groups into a<br>
&gt; &quot;namespace&quot;,<br>
&gt;     for example &quot;Precedence.Assignment&quot;.<br>
&gt;<br>
&gt;<br>
&gt; We don&#39;t have any language features that would allow this.<br>
<br>
</span>&#39;precedencegroup&#39; that is being proposed is a new language feature, we<br>
can choose to use any syntax we like with it.<br>
<div class=""><div class="h5"><br></div></div></blockquote><div><br></div><div>If you&#39;re going to design a new language feature to sink precedence groups into a namespace of their own, you might as well sink them into an unutterable namespace, effectively moving them out of the same namespace as types altogether, no?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">
Dmitri<br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j&lt;i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf(&quot;%d\n&quot;,i);}}} /*Dmitri Gribenko &lt;<a href="mailto:gribozavr@gmail.com">gribozavr@gmail.com</a>&gt;*/<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div></div>