News for hackers. Stuff that matters.
Re:Don’t assume that safety comes for free: a Swift case study by gok on Tuesday December 06, 2016 @09:10PM (#13119957)
&+ isn't quite the same as + in C though. It's defined to perform wrapping overflow everytime, so more like integer + in Java. I don't think there's an addition operator in Swift that means "not only don't do overflow checking, but also consider overflow impossible and optimize accordingly".

Not entirely clear that such an operator is ever what you really want, I suppose...

Re:Don’t assume that safety comes for free: a Swift case study by mikeash on Wednesday December 07, 2016 @10:01AM (#13122968)
I believe you can get that behavior by using + in a file that you compile with -Ounchecked. I don't believe there's any built-in way to do it at an individual call site, short of writing a wrapper that you compile with -Ounchecked and then calling the wrapper where you want that behavior.
Re:Don’t assume that safety comes for free: a Swift case study by gok on Thursday December 08, 2016 @01:17AM (#13128760)
I think you're right, yeah.