On Wed, Apr 24, 2013 at 11:25 AM, Robert O'Callahan <[email protected]>wrote:
> I don't think bignums are useful in a browser because as a browser > developer I will choose data types that cover the ranges of values I want > to handle. If I think I need to handle integer values that don't fit in 32 > bits, I'll use a 64-bit integer type, or a floating point type. Overflow > always means I have a bug*. > Well, in C and C++ it does, and of course that's what most browser developers are going to be used to. If we could rely on checked overflows in Rust, then we could start to lean on that and declare that some tests that trigger overflow are simply tests where task failure is an acceptable result. (Offensive as this may to the cult of correctness, in practice priorities dictate we have to do this kind of thing all the time --- declare that a bug is not worth fixing as long as it's not exploitable.) Rob -- q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
