[RFC] OOP - Destructors #117
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
raph-amiard
reviewed
Feb 18, 2025
| procedure My_Destructor (Self : in out T2); | ||
| end P; | ||
|
|
||
| The destruction sequence works in the following way: |
There was a problem hiding this comment.
I think it is not necessary, and even potentially dangerous to describe the destruction semantics in these terms, because we don't want to define finalization semantics twice. We should just explain how this maps to the Finalizable aspect.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This RFC contains specific elements about the new destructor syntax, coming from the overall OOP discussion.