-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add special function to match lifetimes #5320
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
Merged
chrchr-github
merged 15 commits into
cppcheck-opensource:main
from
pfultz2:match-lifetime
Aug 14, 2023
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
3c02291
Update matching for lifetime
pfultz2 6152ef8
Remove modified changes
pfultz2 08aac77
Rename match function
pfultz2 c48da15
Format
pfultz2 2cdd596
Update tests
pfultz2 b73d9cf
Update function
pfultz2 7e4ee12
Rename function
pfultz2 5826730
Format
pfultz2 eec9156
Merge branch 'main' into match-lifetime
pfultz2 b4610c0
Fix another unit test
pfultz2 d488451
Add comment
pfultz2 7b64167
Fix todo test
pfultz2 cfcc6aa
Remove else
pfultz2 a734360
Remove move
pfultz2 ca9d626
Format
pfultz2 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.
I think that ideally it's better to write a member that is not initialized. It's something explicit that the user can investigate carefully.
Does this PR mean the analysis will be better? Less false negatives or false positives?
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 write the variables when it is partially initialized, but if all members are uninitialized we just write the struct.
Yes because we will track aliases better across all of our analyzers not just
SubExpressionAnalyzer. This should lead to less FPs. And will help enable more FNs in the future as well.