Repository navigation
Fix #6552: false constant value warnings after overloaded extraction #8835
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
Open
tzi4
wants to merge
6
commits into
cppcheck-opensource:main
Choose a base branch
from
tzi4:fix/trac-6552-overloaded-extraction
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
98b27d8
Fix #6552: false constant value warnings after overloaded extraction
tzi4 a9ae535
Preserve value tracking across non-mutating extraction overloads
tzi4 9445993
Use unsigned operands for qualifier masks
tzi4 6ab3555
Simplify overloaded extraction value tracking
tzi4 20c8811
Use RefThunk accessor for Scope::symdb
tzi4 bad40b2
Reduce #6552 tests to one case per branch
tzi4 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
This is an AI review take it with a grain of salt. Please feel free to reject it by clicking on Resolve button
FYI: since f99ea4b on main (#15056, "remove warnings for return result"),
knownConditionTrueFalseis no longer reported forreturn x < 0;. I checked with current main: evenint x = 1; return x < 0;gives no warning. After rebasing, the tests here that expectReturn value 'x<0' is always falsewill fail. Worse, the tests that expect""will pass whether or not the fix works. Usingif (x < 0) {}instead ofreturn x < 0;in these tests should keep them meaningful.