This is an issue that is especially important to me, as I have written a library that also has the goal of making integer arithmetic safe: the bounded::integer library: http://doublewise.net/c++/bounded/ . I presented this library at C++Now 2014 this year. It has a different philosophy from the checked integer type that you described. It instead has compile-time min and max bounds on each integer type, and the goal is to replace all uses of built-in integer types. The result of the arithmetic operators is a new type that is able to hold any result of the operation (so bounded::integer<1, 10> + bounded::integer<4, 7> == bounded::integer<5, 17>). On Tue, Nov 18, 2014 at 11:45 AM, Robert Ramey <ramey@rrsd.com> wrote:
I'm NOT really pushing for this as a boost library
-- View this message in context: http://boost.2283326.n4.nabble.com/safe-numerics-questioning-the-basic-idea-... Sent from the Boost - Dev mailing list archive at Nabble.com.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost