From 622ae41e90e7caad31c71b3299e13b362cf345cd Mon Sep 17 00:00:00 2001 From: Daniel Hofstetter Date: Sun, 26 Oct 2014 16:58:17 +0100 Subject: [PATCH] Guide: Add link to FFI explanation --- src/doc/guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/doc/guide.md b/src/doc/guide.md index c7b8e42b28cd..12df2c548d24 100644 --- a/src/doc/guide.md +++ b/src/doc/guide.md @@ -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