diff options
| author | Wilfred Hughes <me@wilfred.me.uk> | 2017-01-29 10:51:26 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-01-29 10:51:26 +0000 |
| commit | 87bbb3c738e7d351d21fb19b51b2094b5afa0482 (patch) | |
| tree | b75eb3906af1974554e583b392d2464fb8b23ff1 | |
| parent | b37edea656d7dc2e547eeaf1a56fda9254518934 (diff) | |
| download | rust-87bbb3c738e7d351d21fb19b51b2094b5afa0482.tar.gz rust-87bbb3c738e7d351d21fb19b51b2094b5afa0482.zip | |
Minor grammar fix 'can not' -> 'cannot'
The previous version suggested that the compiler chooses not to check, rather than being unable to check.
| -rw-r--r-- | src/doc/book/ffi.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/book/ffi.md b/src/doc/book/ffi.md index 8ab580e6aa9..8d29f11aa05 100644 --- a/src/doc/book/ffi.md +++ b/src/doc/book/ffi.md @@ -56,9 +56,9 @@ almost any function that takes a pointer argument isn't valid for all possible inputs since the pointer could be dangling, and raw pointers fall outside of Rust's safe memory model. -When declaring the argument types to a foreign function, the Rust compiler can -not check if the declaration is correct, so specifying it correctly is part of -keeping the binding correct at runtime. +When declaring the argument types to a foreign function, the Rust compiler +cannot check if the declaration is correct, so specifying it correctly is part +of keeping the binding correct at runtime. The `extern` block can be extended to cover the entire snappy API: |