On Thu, Jun 26, 2014 at 10:30 PM, Daniel Micay <danielmi...@gmail.com> 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) -- Tony Arcieri
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
