rust
/
rfcs
mirror of https://github.com/rust-lang/rfcs
1
0
Fork 0
Code Issues Releases Wiki Activity

Another suggested change to PR additions

This commit is contained in:
Kyle J Strand 2019-09-06 22:21:53 -06:00 committed by GitHub
parent e950faac95
commit dab4e7f5ff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
text/0000-simple_unwind_annotation.md
View File

@ -94,8 +94,8 @@ We should try not to prevent the RFC 2699 or other later RFC from resolving the
The alternatives considered are:
1. Solve the soundness bug by aborting instead of unwinding when reaching an FFI boundary
(https://github.com/rust-lang/rust/issues/52652). As a workaround for applications that would
1. Stabilize the [abort-on-FFI-boundary behavior](https://github.com/rust-lang/rust/issues/52652)
without providing any mechanism to change this behavior. As a workaround for applications that would
otherwise need this unwinding, we would recommend the use of wrappers to translate Rust panics to
and from C ABI-compatible values at FFI boundaries, with a foreign control mechanism like
`setjmp`/`longjmp` or C++ exceptions to skip or unwind segments of foreign stack.