<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 May 23, 2016, at 13:10, Антон Жилин via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">@CoreTeam Please, don't forget to merge pull request with fixes and alternatives from review period.<div class=""><br class=""></div><div class="">@AnyoneElse Today is (formally) the last day of review. It may be your last chance!</div><div class=""><br class=""></div><div class="">Apple repo link:</div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0077-operator-precedence.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0077-operator-precedence.md</a></div><div class=""><br class=""></div><div class="">My repo with some latest changes:</div><div class=""><a href="https://github.com/Anton3/swift-evolution/blob/master/proposals/0077-operator-precedence.md" class="">https://github.com/Anton3/swift-evolution/blob/master/proposals/0077-operator-precedence.md</a><br class=""></div></div></div></blockquote><br class=""></div><div>Thanks for doing this. While I’m a little apprehensive about the implementation, I don’t expect it to be a problem in practice; a DAG is a pretty safe data structure, and the size of the graph (i.e. the number of precedence groups in a program) probably won’t be that big in practice. And it’s so much better than arbitrary precedence numbers.</div><div><br class=""></div><div>To discuss later: what are the naming guidelines for precedence groups? (What part of speech? Why UpperCamelCase?) Are they in a separate scope from normal names? Can you qualify them with module names?</div><div><br class=""></div><div>(Operator declarations in general are weirdly global right now, because they need to be resolvable without doing full lookup work, and because it was easier to implement them that way. So making precedence groups special as well is probably fine, at least for now.)</div><div><br class=""></div><div>Jordan</div></body></html>