Skip to content

Commit 622ae41

Browse files
committed
Guide: Add link to FFI explanation
1 parent cb943b7 commit 622ae41

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/doc/guide.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5288,9 +5288,9 @@ There are two circumstances where Rust's safety provisions don't work well.
52885288
The first is when interfacing with C code, and the second is when building
52895289
certain kinds of abstractions.
52905290

5291-
Rust has support for FFI (which you can read about in the [FFI
5292-
Guide](guide-ffi.html)), but can't guarantee that the C code will be safe.
5293-
Therefore, Rust marks such functions with the `unsafe`
5291+
Rust has support for [FFI](http://en.wikipedia.org/wiki/Foreign_function_interface)
5292+
(which you can read about in the [FFI Guide](guide-ffi.html)), but can't guarantee
5293+
that the C code will be safe. Therefore, Rust marks such functions with the `unsafe`
52945294
keyword, which indicates that the function may not behave properly.
52955295

52965296
Second, if you'd like to create some sort of shared-memory data structure, Rust

0 commit comments

Comments
 (0)