diff options
| author | Nathan Moos <moosingin3space@gmail.com> | 2017-04-29 14:56:35 -0400 |
|---|---|---|
| committer | Nathan Moos <moosingin3space@gmail.com> | 2017-04-29 14:56:35 -0400 |
| commit | 087b838dd2d3cb4e18e0f089cc9886e646d8b49f (patch) | |
| tree | fd9109460a0cce558426eb53b1942c1ee2ea00dd /src/libcore | |
| parent | b4d3ed64ec7f6d7a9fa0530377a29520a90a451f (diff) | |
| download | rust-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.rs | 2 |
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. /// |
