2015-12-17 9:12 GMT+01:00 Robert Ramey
thinking I should eliminate it as it would defeat the whole purpose of the library.
I can see value in such policy. In the e documentation, in section
"Eliminate Runtime Cost" (
https://htmlpreview.github.io/?https://raw.githubusercontent.com/robertramey...)
you show a great application of the library. If I am interested in
improving performance still, I would change the policy form "throw upon
overflow" to "ignore overflow", in hope that the later skips the check
altogether.
Then, using type
safe_signed_range