OpenE2K
/
rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Rollup merge of #31987 - gcatlin:patch-1, r=steveklabnik 

r? @steveklabnik
This commit is contained in:
Steve Klabnik 2016-03-01 13:39:42 -05:00
parent c98c1b777f dcb92abbe1
commit 0ee1b99288
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/doc/book/unsafe.md
View File

@ -4,7 +4,7 @@ Rust’s main draw is its powerful static guarantees about behavior. But safety
checks are conservative by nature: there are some programs that are actually
safe, but the compiler is not able to verify this is true. To write these kinds
of programs, we need to tell the compiler to relax its restrictions a bit. For
this, Rust has a keyword, `unsafe`. Code using `unsafe` has less restrictions
this, Rust has a keyword, `unsafe`. Code using `unsafe` has fewer restrictions
than normal code does.
Let’s go over the syntax, and then we’ll talk semantics. `unsafe` is used in