<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 Aug 2, 2016, at 2:41 PM, Anton Zhilin 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=""><div class="">Here is the proposal draft:</div><a href="https://github.com/Anton3/swift-evolution/blob/remove-precedence-bitwise-arithmetic.md/proposals/NNNN-remove-precedence-bitwise-arithmetic.md" class="">https://github.com/Anton3/swift-evolution/blob/remove-precedence-bitwise-arithmetic.md/proposals/NNNN-remove-precedence-bitwise-arithmetic.md</a><br class=""><div class=""><br class=""></div><div class="">Motivation will be the most difficult section here.</div></div></div></blockquote><div><br class=""></div></div>Yes, it will. Some 2c to consider:<div class=""><br class=""></div><div class="">1) Swift 4 is being designed with the ability to all us to make “source changes" that don’t break existing source code.</div><div class=""><br class=""></div><div class="">2) It is really important that we continue to polish the language to make it great for the long term, so the spirit of your proposal is great to explore.</div><div class=""><br class=""></div><div class="">3) That said, any source breaking change needs to be *very* strongly motivated. To make this change, you should find evidence of common bugs that would be solved by this, evidence of actual user confusion in practice, etc.</div><div class=""><br class=""></div><div class="">4) Assuming all of the above works out, we still won’t be able to evaluate the proposal until we have the exact details of how the “source stability” model works. Until we have that model, we don’t know that this proposal will be able to be covered by it.</div><div class=""><br class=""></div><div class="">On #4, I’m pretty certain that we will be fine, but until we have the model nailed down, we procedurally can’t even have the formal review period. In any case, you need to build a specific proposal with very strong rationale first. :-)</div><div class=""><br class=""></div><div class="">-Chris</div></body></html>