C++: Exclude copy assignment in LargeParameter.ql#752
Merged
Conversation
The purpose of the copy assignment operator is to copy the object, so we should not complain that a copy happens when passing the parameter. See https://en.wikibooks.org/wiki/More_C++_Idioms/Copy-and-swap for details.
Contributor
|
I note the failing language test appears to be the one removed by #747, and has nothing to do with this PR. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 addresses https://discuss.lgtm.com/t/c-consider-passing-a-pointer-to-unifying-assignment-operator/1664. I've checked that the new version of the query makes the alert go away on the affected project: https://lgtm.com/query/5725802104708838857/