C++: Don't strip specifiers away in TFinalParameterUse
#15626
Merged
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 is a preparatory change to an upcoming PR I'm doing related to the "automatically block flow out of modelled functions" work. It won't really have any visible impact yet, so it should be a totally safe change.
The core of the change is that we were incorrectly calling
getUnspecifiedType
instead ofgetUnderlyingType
when checking whether a parameter could be written to. CallinggetUnspecifiedType
is wrong since, in addition to resolve typedefs, it also strips offconst
specifiers.Instead, we should be calling
getUnderlyingType
since that only resolves typedefs.DCA looks uneventful (as expected).