<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 2, 2016 at 1:07 PM, Anton Zhilin <span dir="ltr"><<a href="mailto:antonyzhilin@gmail.com" target="_blank">antonyzhilin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div class="gmail_extra"><div class="gmail_quote">2016-08-02 19:08 GMT+03:00 Xiaodi Wu <span dir="ltr"><<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">That's an excellent point, actually. Would there be downsides not yet considered?<div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 2, 2016 at 11:03 Félix Cloutier <<a href="mailto:felixcca@yahoo.ca" target="_blank">felixcca@yahoo.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">These expressions mix two types of logic that have different implications. For instance, `a * 16` and `a << 4` are "mostly equivalent", except that `a * 16` will crash on overflow. In these cases, I find that grouping provides some visual insulation that groups off the somewhat subtle differences.<div></div></div><div style="word-wrap:break-word"><div><div>
<br><span style="color:rgb(0,0,0);font-family:"lucida grande";font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline">Félix</span></div></div></div></blockquote></div>
</div></div></blockquote></div><br></div></span><div class="gmail_extra">So it at least makes sense to create a proposal about this:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">RangeFormation < Addition < Multiplication</div><div class="gmail_extra">RangeFormation < BitwiseOr < BitwiseAnd < BitwiseShift</div><div class="gmail_extra"><br></div><div class="gmail_extra">Pretty much everyone says that moving Ternary below Assignment would be a regression.</div><div class="gmail_extra">I feel like a bit more discussion is needed on this:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Another concern is NilCoalescing, which can be thought to be semantically similar to Ternary. And at the same time it looks like || and &&, which would bring it between LogicalConjunction and Comparison.<span class=""><br>Also, do Casting and RangeFormation stand where they should?</span></blockquote><div><br></div><div>Someone said that this is actually not what was planned -- sure, it may need a separate proposal and a separate thread, but I think it's OK to use this one for now.</div></div></div></div></blockquote><div><br></div><div>Anton, since this list is high-volume, people may skip entire conversations because the subject line is not of interest to them. If you're going to discuss additional topics, please do start new threads. That way, we can get the maximum participation.</div></div><br></div></div>