Correct and expand documentation of handle_alloc_error
and set_alloc_error_hook
.
#115007
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 primary goal of this change is to remove the false claim that
handle_alloc_error
always aborts; instead, code should be prepared forhandle_alloc_error
to possibly unwind, and be sound under that condition.I saw other opportunities for improvement, so I have added all the following information:
handle_alloc_error
may panic instead of aborting. (Fixes Clarify thathandle_alloc_error
may unwind #114898)I've checked these statements against the source code of
alloc
andstd
, but there may be nuances I haven't caught, so a careful review is welcome.