mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor grammar fix 'can not' -> 'cannot'

Browse Source 
The previous version suggested that the compiler chooses not to check, rather than being unable to check.
This commit is contained in:
Wilfred Hughes 2017-01-29 10:51:26 +00:00 committed by GitHub
parent b37edea656
commit 87bbb3c738
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/book/ffi.md
View File

@ -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 inputs since the pointer could be dangling, and raw pointers fall outside of
Rust's safe memory model. Rust's safe memory model.
When declaring the argument types to a foreign function, the Rust compiler can When declaring the argument types to a foreign function, the Rust compiler
not check if the declaration is correct, so specifying it correctly is part of cannot check if the declaration is correct, so specifying it correctly is part
keeping the binding correct at runtime. of keeping the binding correct at runtime.
The `extern` block can be extended to cover the entire snappy API: The `extern` block can be extended to cover the entire snappy API: