Untitled attachment

Notices where this attachment appears

1. namark (namark@qoto.org)'s status on Sunday, 09-Jan-2022 18:10:37 UTC namark

   in reply to

   @codewiz you seemed to have a problem with the concept so that was an explanation and a proof of concept implementation. Pleasantly surprised it worked at all! If you care about it you should participate, cause as far as I know that is the most developed of any such concepts:
   https://github.com/boostorg/safe_numerics

   common_type trait sounds like a misnomer, but I imagine chrono didn't have anything better to use. safe_numeric may provide alternatives on that front, though it will likely never be standardized in it's current form. It's much more likely for a more generic numeric library to get in, that would also handle arbitrary precision and provide the safe_numerics functionality as its subset, and probably not called "safe" cause that's not a very good name either.