Skip to content

Commit

Permalink
Copyedits to FFI and unwinding section
Browse files Browse the repository at this point in the history
These are minor changes that make the text flow better to me.
  • Loading branch information
tmandry authored Jan 14, 2023
1 parent 960d610 commit 94bb6a6
Showing 1 changed file with 11 additions and 8 deletions.
19 changes: 11 additions & 8 deletions src/ffi.md
Original file line number Diff line number Diff line change
Expand Up @@ -722,16 +722,19 @@ No `transmute` required!
## FFI and unwinding
It’s important to be mindful of unwinding when working with FFI. Each
non-`Rust` ABI comes in two variants, one with `-unwind` suffix and one without. If
you expect Rust `panic`s or foreign (e.g. C++) exceptions to cross an FFI
boundary, that boundary must use the appropriate `-unwind` ABI string (note
that compiling with `panic=abort` will still cause `panic!` to immediately
abort the process, regardless of which ABI is specified by the function that
`panic`s).
ABI comes in two variants, one with `-unwind` suffix and one without (except
the `Rust` ABI, which always permits unwinding).
If you expect Rust `panic`s or foreign (e.g. C++) exceptions to cross an FFI
boundary, that boundary must use the appropriate `-unwind` ABI string.
Conversely, if you do not expect unwinding to cross an ABI boundary, use one of
the non-`unwind` ABI strings (other than `Rust`, which always permits
unwinding). If an unwinding operation does encounter an ABI boundary that is
the non-`unwind` ABI strings.
> Note: Compiling with `panic=abort` will still cause `panic!` to immediately
abort the process, regardless of which ABI is specified by the function that
`panic`s.
If an unwinding operation does encounter an ABI boundary that is
not permitted to unwind, the behavior depends on the source of the unwinding
(Rust `panic` or a foreign exception):
Expand Down

0 comments on commit 94bb6a6

Please sign in to comment.