You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You wrote recently that you don't want checked_arithmetic by default, since this is in the first instance a library for type safety. I understand that, and probably checked arithmetic on unsigned types might also introduce errors.
However, since safe arithmetics are a closely related and important issue, I think they should be available with equal precedence, e.g. to make use of the literal operators to get types with checked arithmetics. This should be a simple change, like creating a new macro TYPE_SAFE_ARITHMETIC_CHECKED.
If you want, I can make a PR.
The text was updated successfully, but these errors were encountered:
You wrote recently that you don't want
checked_arithmetic
by default, since this is in the first instance a library for type safety. I understand that, and probably checked arithmetic on unsigned types might also introduce errors.However, since safe arithmetics are a closely related and important issue, I think they should be available with equal precedence, e.g. to make use of the literal operators to get types with checked arithmetics. This should be a simple change, like creating a new macro
TYPE_SAFE_ARITHMETIC_CHECKED
.If you want, I can make a PR.
The text was updated successfully, but these errors were encountered: