about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-06-27 14:53:15 +0000
committerbors <bors@rust-lang.org>2015-06-27 14:53:15 +0000
commit2ba46f8bbc6fdf10e434faea52b9ca20e0d9f2eb (patch)
treec64523a6c190e5bc6399baf2dbef3f6048af1c07 /src/doc
parentb36ae019468c36c995523d797446a372ab9d14e1 (diff)
parent6dd33b459b30b65a75f644a75169cb6a07e4df53 (diff)
downloadrust-2ba46f8bbc6fdf10e434faea52b9ca20e0d9f2eb.tar.gz
rust-2ba46f8bbc6fdf10e434faea52b9ca20e0d9f2eb.zip
Auto merge of #26616 - Manishearth:rollup, r=Manishearth
- Successful merges: #26565, #26584, #26596, #26603
- Failed merges: 
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/reference.md3
-rw-r--r--src/doc/trpl/unsafe.md7
2 files changed, 2 insertions, 8 deletions
diff --git a/src/doc/reference.md b/src/doc/reference.md
index a3e13acccae..7e28651c6aa 100644
--- a/src/doc/reference.md
+++ b/src/doc/reference.md
@@ -1047,11 +1047,8 @@ This is a list of behavior not considered *unsafe* in Rust terms, but that may
 be undesired.
 
 * Deadlocks
-* Reading data from private fields (`std::repr`)
 * Leaks of memory and other resources
 * Exiting without calling destructors
-* Sending signals
-* Accessing/modifying the file system
 * Integer overflow
   - Overflow is considered "unexpected" behavior and is always user-error,
     unless the `wrapping` primitives are used. In non-optimized builds, the compiler
diff --git a/src/doc/trpl/unsafe.md b/src/doc/trpl/unsafe.md
index fdb9c33a2b0..e8f1b829061 100644
--- a/src/doc/trpl/unsafe.md
+++ b/src/doc/trpl/unsafe.md
@@ -12,7 +12,7 @@ two contexts. The first one is to mark a function as unsafe:
 
 ```rust
 unsafe fn danger_will_robinson() {
-    // scary stuff 
+    // scary stuff
 }
 ```
 
@@ -68,11 +68,8 @@ Whew! That’s a bunch of stuff. It’s also important to notice all kinds of
 behaviors that are certainly bad, but are expressly _not_ unsafe:
 
 * Deadlocks
-* Reading data from private fields
-* Leaks due to reference count cycles
+* Leaks of memory or other resources
 * Exiting without calling destructors
-* Sending signals
-* Accessing/modifying the file system
 * Integer overflow
 
 Rust cannot prevent all kinds of software problems. Buggy code can and will be