[AST] Use explicit type erasure in TypeSourceInfo constructor #68435
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.
When this file is included in a project compiled with GCC 13
-Werror
, compilation fails with the following diagnostic:To avoid this, we add an explicit type cast. The cast to
void*
makes sense, since other member functions ofTypeSourceInfo
also treat the buffer(this + 1)
of lengthDataSize
as opaque memory, and was likely left out by mistake.Fixes: 4498663 ("[AST] Initialized data after TypeSourceInfo")
I also suggest to apply this to release/17.x if possible.