Fix bugzilla 24596: std.typecons.Rebindable2: Don't destroy classes! Only destroy structs! #9012
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.
PR fixes #8768 for classes.
object.destroy
is, perhaps appropriately, the most destructive function ever written.It does something useful (resetting the value and calling the destructor) for structs and struct derivatives, but something horrible (destroying the class data) for objects. So you're always tempted to use it, but you have to remember, every time, to disable the cases where it silently causes future crashes.
I forgot this time.
edit:
core.internal.container.common.destroy
looks like it does it right... Maybe I just switch to that? Is that safe to call fromstd.typecons
?