4 ms·
In Swift, you have total control over this. If you want checks, use +. If you don't want checks, use &+. In Rust, the operators check in debug builds, and wrap
by mikeash 10y ago
In Swift, you have total control over this. If you want checks, use +. If you don't want checks, use &+.
In Rust, the operators check in debug builds, and wrap in release builds. Calls are provided so you can always have them check, or always have them wrap, if you need it.
Note that C has some really ugly behavior here. Signed overflow is undefined behavior, which means that the compiler doesn't need to check for it, but also that it can assume it never happens and optimized based on that. Many programmers don't realize this, or don't notice that they've accidentally written code that depends on overflow behavior, which can lead to many entertaining bugs: https://lwn.net/Articles/511259/ https://lwn.net/Articles/511259/
- deleted 10y ago[deleted]
- dispose13432 10y ago>Note that C has some really ugly behavior here. Signed overflow is undefined behavior, which means that the compiler doesn't need to check for it, but also that it can assume it never happens and optimized based on that. Many programmers don't realize this, or don't notice that they've accidentally written code that depends on overflow behavior, which can lead to many entertaining bugs: https://lwn.net/Articles/511259/ https://lwn.net/Articles/511259/ That's because different CPUs behave differently. To avoid undefined behavior, you have to have an "if" at every +.
- tomovo 10y agoSarcarsm? In some cases you can just do sanity checks on your inputs and use larger number formats for doing sums. Depends on the use case.
- jandrese 10y agoYou would also be hard pressed to find a modern architecture that doesn't use twos complement for signed integers. That said, rolling over on a signed integer is almost always an error, although luckily it is usually one of the easier ones to detect in the debugger. Big negative numbers are a dead giveaway.
- dispose13432 10y agoIt's easy to detect in the debugger. The danger is signed int x; cin>>x; if(x+1<x){return OVERFLOW;} will, in modern optimizing compilers, never return OVERFLOW There were quite a few security holes introduced by the compiler with that. ----- The only problem is to make a standard, one has to define that MAX_INT+1 = 0 or something. Then, whenever one does signed int x; cin>> x; signed int y = x+1; really turns into signed int = 0; if ( x < MAX_INT) y= x+1 else y = 1;
- ArkyBeagle 10y ago"Many programmers don't realize this..." ( bangs head with ball-peen hammer; rends garment )
- gok 10y ago&+ 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...
- mikeash 10y agoI 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.
- gok 10y agoI think you're right, yeah.