<div dir="ltr"><span style="font-size:13px"> * What is your evaluation of the proposal?</span><div>+1<br style="font-size:13px"><span style="font-size:13px"> * Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div>Yes. Definitely. Operator overloading is currently fine in only the simplest of cases.<br style="font-size:13px"><span style="font-size:13px"> * Does this proposal fit well with the feel and direction of Swift?</span></div><div>I think so, yes. <br style="font-size:13px"><span style="font-size:13px"> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div>No<br style="font-size:13px"><span style="font-size:13px"> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br></div><div><span style="font-size:13px"><br></span></div><div>I followed the original thread and have been wrangling precedence for a while now.</div><div><br></div><div><br></div><div><br></div><div>One problem that I have encountered with operators that I think still needs solving is operators from different libraries colliding with regard to precedence.</div><div><br></div><div>`^` is the example that bit me most recently. Swift has one with left fixity at 160. I wanted to overload it with right fixity for math operators. The only way that I have thought involves </div><div>- precedence groups are tied to a module</div><div>- overloads in modules are tied to specific precedence groups.</div><div><br></div><div>I have *not a clue* about how feasible this solution is, but it would allow greater flexibility and, at least in my opinion, more understandable behavior. Attempting to overload `^` right now, especially with right fixity, results in confusing behavior.</div><div><br></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 11:30 PM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Swift community,<br>
<br>
The review of "SE-0077: Improved operator declarations" begins now and runs through May 23. The proposal is available here:<br>
<br>
<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>
<br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br>
<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>
<br>
or, if you would like to keep your feedback private, directly to the review manager.<br>
<br>
What goes into a review?<br>
<br>
The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br>
<br>
* What is your evaluation of the proposal?<br>
* Is the problem being addressed significant enough to warrant a change to Swift?<br>
* Does this proposal fit well with the feel and direction of Swift?<br>
* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
More information about the Swift evolution process is available at<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br>
<br>
Thank you,<br>
<br>
-Chris Lattner<br>
Review Manager<br>
<br>
<br>
<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>
</blockquote></div><br></div>