Skip to content

Commit 49e09ee

Browse files
alexcrichtonManishearth
authored andcommitted
std: Stabilize the prelude module
This commit is an implementation of [RFC 503][rfc] which is a stabilization story for the prelude. Most of the RFC was directly applied, removing reexports. Some reexports are kept around, however: * `range` remains until range syntax has landed to reduce churn. * `Path` and `GenericPath` remain until path reform lands. This is done to prevent many imports of `GenericPath` which will soon be removed. * All `io` traits remain until I/O reform lands so imports can be rewritten all at once to `std::io::prelude::*`. This is a breaking change because many prelude reexports have been removed, and the RFC can be consulted for the exact list of removed reexports, as well as to find the locations of where to import them. [rfc]: https://github.com/rust-lang/rfcs/blob/master/text/0503-prelude-stabilization.md [breaking-change] Closes rust-lang#20068
1 parent b81216e commit 49e09ee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4149,11 +4149,11 @@ Unwinding the stack of a thread is done by the thread itself, on its own control
41494149
stack. If a value with a destructor is freed during unwinding, the code for the
41504150
destructor is run, also on the thread's control stack. Running the destructor
41514151
code causes a temporary transition to a *running* state, and allows the
4152-
destructor code to cause any subsequent state transitions. The original thread
4152+
destructor code to cause any subsequent state transitions. The original thread
41534153
of unwinding and panicking thereby may suspend temporarily, and may involve
41544154
(recursive) unwinding of the stack of a failed destructor. Nonetheless, the
41554155
outermost unwinding activity will continue until the stack is unwound and the
4156-
thread transitions to the *dead* state. There is no way to "recover" from thread
4156+
thread transitions to the *dead* state. There is no way to "recover" from thread
41574157
panics. Once a thread has temporarily suspended its unwinding in the *panicking*
41584158
state, a panic occurring from within this destructor results in *hard* panic.
41594159
A hard panic currently results in the process aborting.

0 commit comments

Comments
 (0)