about summary refs log tree commit diff
path: root/src/libcore
diff options
context:
space:
mode:
authorNathan Moos <moosingin3space@gmail.com>2017-04-29 14:56:35 -0400
committerNathan Moos <moosingin3space@gmail.com>2017-04-29 14:56:35 -0400
commit087b838dd2d3cb4e18e0f089cc9886e646d8b49f (patch)
treefd9109460a0cce558426eb53b1942c1ee2ea00dd /src/libcore
parentb4d3ed64ec7f6d7a9fa0530377a29520a90a451f (diff)
downloadrust-087b838dd2d3cb4e18e0f089cc9886e646d8b49f.tar.gz
rust-087b838dd2d3cb4e18e0f089cc9886e646d8b49f.zip
process:exit -> process::exit in mem::forget docs
The documentation in mem::forget says "...or call `process:exit`..."
instead of `process::exit`.

r? @steveklabnik
Diffstat (limited to 'src/libcore')
-rw-r--r--src/libcore/mem.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/mem.rs b/src/libcore/mem.rs
index 7be927b28ed..b397aba6b92 100644
--- a/src/libcore/mem.rs
+++ b/src/libcore/mem.rs
@@ -40,7 +40,7 @@ pub use intrinsics::transmute;
 /// `forget` is not marked as `unsafe`, because Rust's safety guarantees
 /// do not include a guarantee that destructors will always run. For example,
 /// a program can create a reference cycle using [`Rc`][rc], or call
-/// [`process:exit`][exit] to exit without running destructors. Thus, allowing
+/// [`process::exit`][exit] to exit without running destructors. Thus, allowing
 /// `mem::forget` from safe code does not fundamentally change Rust's safety
 /// guarantees.
 ///