Expand first-in-book use of certain abbreviations

- Expand first-in-book use of foreign function interface (FFI) in
safe-unsafe-meaning.md
- Expand first-in-book use of application binary interface (ABI) in
other-reprs.md
pull/40/head
Henri Lunnikivi 7 years ago
parent cfb1f2d7e5
commit 60d2621b32

@ -37,10 +37,10 @@ still consumes a byte of space.
difference from a struct is that the fields arent named.
* This is equivalent to one of `repr(u*)` (see the next section) for enums. The
chosen size is the default enum size for the target platform's C ABI. Note that
enum representation in C is implementation defined, so this is really a "best
guess". In particular, this may be incorrect when the C code of interest is
compiled with certain flags.
chosen size is the default enum size for the target platform's C application
binary interface (ABI). Note that enum representation in C is implementation
defined, so this is really a "best guess". In particular, this may be incorrect
when the C code of interest is compiled with certain flags.
* "C-like" enums with `repr(C)` or `repr(u*)` still may not be set to an
integer value without a corresponding variant, even though this is

@ -38,8 +38,8 @@ The standard library has a number of unsafe functions, including:
type safety in arbitrary ways (see [conversions] for details).
* Every raw pointer to a sized type has an `offset` method that
invokes Undefined Behavior if the passed offset is not ["in bounds"][ptr_offset].
* All FFI functions are `unsafe` to call because the other language can do
arbitrary operations that the Rust compiler can't check.
* All FFI (Foreign Function Interface) functions are `unsafe` to call because the
other language can do arbitrary operations that the Rust compiler can't check.
As of Rust 1.0 there are exactly two unsafe traits:

Loading…
Cancel
Save