Fixed issue 534 #535
Open
Fixed issue 534 #535
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The original explanation of moving ownership was concise but left room for confusion due to a lack of detail and clarity. The following issues were identified:
It didn’t clarify the difference between memory stored on the stack and memory on the heap.
There was no detailed explanation of the Drop mechanism or when memory is released.
Terms such as "ownership," "move," and "drop" were used inconsistently and without sufficient explanation.
There was no example to clearly demonstrate the runtime behavior of ownership and dropping.
Improved clarity and structure and added memory details.