diff options
| author | Corey Farwell <coreyf@rwell.org> | 2017-04-29 23:44:30 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-29 23:44:30 -0400 |
| commit | eab2af9af517ab9e22ae269e5787bee93e599d0d (patch) | |
| tree | 7c54c4cfab6625a0584f5abeba5e4dc179f86372 /src | |
| parent | c9f5a47ed1b39de6a833e35603c32d434031cc4e (diff) | |
| parent | 087b838dd2d3cb4e18e0f089cc9886e646d8b49f (diff) | |
| download | rust-eab2af9af517ab9e22ae269e5787bee93e599d0d.tar.gz rust-eab2af9af517ab9e22ae269e5787bee93e599d0d.zip | |
Rollup merge of #41636 - moosingin3space:fix/process-exit-in-forget-doc, r=sfackler
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')
| -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. /// |