Fix compiler-inserted destructor call on shared objects #6752
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.
Currently, a struct can be used as both shared and not when the constructor (and other functions) are templated on this. Defining a destructor breaks this because destructors can't be templated, and the non-shared destructor call on a shared
thisfails. This patch fixes this in a manner similar to how the compiler already treats destructor calls onimmutableandconstobjects: by casting it away.Since the compiler-generated destructor call is always scoped, only one thread is destroying it anyway.