Add upper-bound overflow checker for StaticCast
#454
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This completes our overflow checking capabilities for
StaticCast
, inthe obvious way.
Note that we have a different set of subtleties to wrestle with than for
the min. For the min, we had to deal with unsigned types having a lower
bound of 0, although the signed types' lower bounds were nice powers of
two. For the max, in this PR, we have to watch out for the upper bounds
being slightly lower than a nice power of two. This has surprising
consequences, such as the fact that you can cast an int type's max to a
floating point type, but you can't cast it back. We deal with these
as best we can, bearing in mind that many common tools for dealing with
floating point types are not available in
constexpr
for C++14.Helps #349.