diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2016-01-11 08:48:35 -0500 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2016-01-11 14:19:51 -0500 |
| commit | eb2343f25b07dd1760d50546d7979a39c363ff09 (patch) | |
| tree | b729567584fef47e0d0d4acbf7e0118eca2625f3 /src | |
| parent | d228cd3964b7cbac7665ff38bde46da67586b87d (diff) | |
Be a bit more correct about segfault causality
Fixes #30819
Diffstat (limited to 'src')
| -rw-r--r-- | src/doc/book/unsafe.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/book/unsafe.md b/src/doc/book/unsafe.md index 1b223365bd6..63e92316f37 100644 --- a/src/doc/book/unsafe.md +++ b/src/doc/book/unsafe.md @@ -41,8 +41,8 @@ unsafe impl Scary for i32 {} ``` It’s important to be able to explicitly delineate code that may have bugs that -cause big problems. If a Rust program segfaults, you can be sure it’s somewhere -in the sections marked `unsafe`. +cause big problems. If a Rust program segfaults, you can be sure the cause is +related to something marked `unsafe`. # What does ‘safe’ mean? |