Conversation
|
cc @Amanieu, @folkertdev, @sayantn
cc @rust-lang/rustfmt Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter cc @rust-lang/miri, @RalfJung, @oli-obk, @lcnr
cc @rust-lang/miri
cc @bjorn3 |
|
|
This comment has been minimized.
This comment has been minimized.
f9baace to
bdc9dac
Compare
This comment has been minimized.
This comment has been minimized.
|
Ah yeah sorry! Trim on save got me of course. |
bdc9dac to
bfade6d
Compare
This comment has been minimized.
This comment has been minimized.
The semantics of `intrinsics::abort()` are closer to what we have unstably as `abort_immediate()` than to `process::abort()` or `libc::abort()`. Rename it to make more clear that the intrinsic is more of an intentional crash with platform-specific behavior than what `libc::abort()` tries to be (i.e. raising `SIGABRT`).
bfade6d to
4a133bf
Compare
|
I agree with the change but don't have time to review it, sorry. |
|
@rustbot ready |
|
@bors r+ rollup Strong agree that we should try to rename intrinsics to match their stable counterparts. It just is a lot of effort that many folks don't want to put in. Thanks for doing this. |
|
This pull request was unapproved. |
|
☔ The latest upstream changes (presumably #163630) made this pull request unmergeable. Please resolve the merge conflicts by rebasing. |
The semantics of
intrinsics::abort()are closer to what we have unstably asabort_immediate()than toprocess::abort()orlibc::abort(). Rename it to make more clear that the intrinsic is more of an intentional crash with platform-specific behavior than whatlibc::abort()tries to be (i.e. raisingSIGABRT).If desired, a new intrinsic like
abort_gracefullycould be introduced that performs platform-specific behavior. This would more cleanly unblock #149780.See also discussion at the tracking issue for
immediate_abort#154601.r? @RalfJung I suppose