Very well. May I ask what the rationale might be? I'm not sure I can deduce it from the available documentation. In other circumstances where Swift operators differ from C (e.g. overflow handling for addition, etc.), the behavior is amply documented and the rationale quite clear. (I should add that Swift documentation currently introduces these bitwise operators as 'familiar' to those coming from C and Objective-C before defining what they are, which discourages careful study.)<br><div class="gmail_quote"><div dir="ltr">On Sat, Feb 13, 2016 at 10:10 PM Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Feb 13, 2016, at 6:32 AM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Not sure if this is intentional, a bug, and/or a topic for evolution:<br>
><br>
> In Swift, bitwise operators seem to have a different precedence in<br>
> relation to other operators than they do in (all other?) C-family<br>
> languages, at least per documentation.<br>
<br>
Yep, this is true, and this is intentional. Swift has a greatly simplified and rationalized set of precedences, and yes, that means they differ from C.<br>
<br>
-Chris<br>
<br>
</blockquote></div>