mathieu/granite-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Guide: Add link to FFI explanation

Browse source
This commit is contained in:
Daniel Hofstetter 2014-10-26 16:58:17 +01:00
parent cb943b7d2b
commit 622ae41e90
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/doc/guide.md
View file

@ -5288,9 +5288,9 @@ There are two circumstances where Rust's safety provisions don't work well.
The first is when interfacing with C code, and the second is when building
certain kinds of abstractions.
Rust has support for FFI (which you can read about in the [FFI
Guide](guide-ffi.html)), but can't guarantee that the C code will be safe.
Therefore, Rust marks such functions with the `unsafe`
Rust has support for [FFI](http://en.wikipedia.org/wiki/Foreign_function_interface)
(which you can read about in the [FFI Guide](guide-ffi.html)), but can't guarantee
that the C code will be safe. Therefore, Rust marks such functions with the `unsafe`
keyword, which indicates that the function may not behave properly.
Second, if you'd like to create some sort of shared-memory data structure, Rust