[include-cleaner] Turn new/delete usages to ambiguous references #105844
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.
In practice most of these expressions just resolve to implicitly
provided
operator new
and standard says it's not necessary to include<new>
for that.Hence this is resulting in a lot of churn in cases where inclusion of
<new>
doesn't matter, and might even be undesired by the developer.By switching to an ambiguous reference we try to find a middle ground
here, ensuring that we don't drop providers of
operator new
when thedeveloper explicitly listed them in the includes, and chose to believe
it's the implicitly provided
operator new
and don't insert an includein other cases.