rollup merge of #24640: steveklabnik/new_unsafe_guide
https://github.com/rust-lang/rust/pull/24631 is related, as it will delete this from the TOC, but I want to keep it here.
This commit is contained in:
commit
1ec7ccb53c
|
@ -55,6 +55,7 @@
|
|||
* [Deref coercions](deref-coercions.md)
|
||||
* [Macros](macros.md)
|
||||
* [Raw Pointers](raw-pointers.md)
|
||||
* [`unsafe`](unsafe.md)
|
||||
* [Nightly Rust](nightly-rust.md)
|
||||
* [Compiler Plugins](compiler-plugins.md)
|
||||
* [Inline Assembly](inline-assembly.md)
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
% Unsafe Code
|
||||
% Unsafe
|
||||
|
||||
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
|
||||
|
@ -76,7 +76,7 @@ behaviors that are certainly bad, but are expressly _not_ unsafe:
|
|||
* Integer overflow
|
||||
|
||||
Rust cannot prevent all kinds of software problems. Buggy code can and will be
|
||||
written in Rust. These things arne’t great, but they don’t qualify as `unsafe`
|
||||
written in Rust. These things aren’t great, but they don’t qualify as `unsafe`
|
||||
specifically.
|
||||
|
||||
# Unsafe Superpowers
|
|
@ -208,7 +208,7 @@ fn main() {
|
|||
unsafe { f(); }
|
||||
}
|
||||
|
||||
See also http://doc.rust-lang.org/book/unsafe-code.html
|
||||
See also http://doc.rust-lang.org/book/unsafe.html
|
||||
"##,
|
||||
|
||||
E0152: r##"
|
||||
|
|
Loading…
Reference in New Issue