fix: wrong code generation for synthesized object hooks #1338
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.
Summary
Fix a bug with synthesis of lifetime-tracking hooks for object types
using inheritance, which showed up as a C compiler error when using
recent versions of clang or gcc.
Fixes #1337.
Details
When synthesizing the hooks for object types using inheritance, the
destination accessor expression wasn't wrapped in an object conversion
prior to emitting the parent object handling.
Without the conversion, the synthesized hook passed along its own
parameter to the call of the super type's hook as-is. This is wrong
in general (the argument's type doesn't match the parameter's), but
didn't cause concrete issues until gcc and clang started to disallow
implicit conversions between incompatible pointer types.