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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++: Constant type-bounds in the new range analysis #13783
C++: Constant type-bounds in the new range analysis #13783
Changes from all commits
050a563
b14db86
9807c0b
2d832db
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've trouble following this. Why os this restricted to
SemTypeReason
only?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because
semHasConstantBoundConstantSpecific
only infers bounds based on type information. It's probably possible to push this condition intosemHasConstantBoundConstantSpecific
, but that then requires thatsemHasConstantBoundConstantSpecific
knows about theSemReason
type which it currently doesn't since that predicate is defined outside theCppLangImplConstant
module (which instantiates those types).Does that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So zero bounds are not constant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
semHasConstantBoundConstantSpecific
just forwards tohasConstantBoundConstantSpecific
(which is the predicate added here). The only thing that adds is the type bounds inferred from type conversions.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We briefly discussed this face-to-face. This is the correct thing to do here because as Mathias writes:
We could extend this later and push down the
reason
argument, but that is not of immediate concern here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 verified experimentally