On 27/06/14 01:38 AM, Tony Arcieri wrote: > On Thu, Jun 26, 2014 at 10:30 PM, Daniel Micay <[email protected] > <mailto:[email protected]>> wrote: > > It's a perfect example of a case where this feature wouldn't have > helped. Performance critical loops with years of micro-optimization are > not going to use checked arithmetic types. Every branch that the > programmer thinks can be avoided will be avoided. > > > I know you're not fans of a compiler flag, but a checked debug build > with traps you can optimize out in an optimized build could've caught it. > > As it were, this is what Swift provides (in addition to explicit > overflow operators)
It doesn't happen on inputs that aren't pathological, a debug build with checked overflow wouldn't have caught this. No one had considered this issue and there was no test for it.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
