au
au copied to clipboard
Separate risk checks for overflow and truncation
Given a conversion from one (unit, rep) to another, we should reason separately about overflow and truncation risks. This will pave the way for new APIs in #122.
Note: we should add this kind of argument not just everywhere we currently let users say "coerce", but also for the as_raw_number utility.
Blocked on #349, which is under active development.