Improve compile-time constraints for constants #72
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.
Since there is no facility in the standard to tell if an expression is evaluated at compile-time (like
noexcept(expr)
), we used to usestd::is_nothrow_constructible
in the implementation ofproxy
. It is not equivalent to that a value could be constructed at compile-time. We did a little trickis_consteval
in this change to improve the constraints. Somenoexcept
in the reflection types in unit tests are removed (reverted from the last PR). 2 test cases are added.