Split set_alloc_error_hook#159702
Conversation
|
@bors squash |
This comment has been minimized.
This comment has been minimized.
|
🔨 2 commits were squashed into 649e2f3. |
224949f to
649e2f3
Compare
|
@bors r+ rollup |
|
🦫 |
This comment has been minimized.
This comment has been minimized.
|
This pull request was unapproved. |
a2ab508 to
8e3cc4e
Compare
|
passed locally. @bors r=jhpratt rollup |
8e3cc4e to
1cf8cce
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@bors r=jhpratt rollup |
…hpratt Split `set_alloc_error_hook` Per libs-api consensus in rust-lang/libs-team#834; modifies rust-lang#51245. r? libs
|
one more rejection, docs need changing. sorry jonathan :< @bors r- |
|
This pull request was unapproved. This PR was contained in a rollup (#159709), which was unapproved. |
|
This PR was contained in a rollup (#159709), which was closed. |
Co-authored-by: Ralf Jung <[email protected]>
| /// configuration for all panics), or abort the process (with no unwinding). | ||
| /// Callers may assume that this function always aborts execution. However, implementors that do not | ||
| /// rely on this invariant are encouraged to document this in order to be compatible with users of | ||
| /// [`set_alloc_error_hook_unwinding`]. |
There was a problem hiding this comment.
cc @rust-lang/libs-api - this does need fcp after all (see discussion on zulip)
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
@maxdexh correctly points out that this tells clients of the global allocator to call handle_alloc_error, not global allocators themselves. Sorry for the noise.
This comment was marked as outdated.
This comment was marked as outdated.
|
wow this turned out to be controversial. i'll let this bake for a bit i guess since it seems to be a bit broader than just a team nomination |
View all comments
Per libs-api consensus in rust-lang/libs-team#834; modifies #51245.
r? libs