mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-25 16:24:46 +00:00
Rollup merge of #117168 - oli-obk:coroutine_cleanups, r=JohnTitor
Fix some coroutine sentences that don't make sense anymore. These happened during the `generator` -> `coroutine` rename. Found thanks to `@pthariensflame` for their thorough review of the `generator` -> `coroutine` rename https://github.com/rust-lang/rust/pull/116958#issuecomment-1777756937
This commit is contained in:
commit
a7d05a6dfa
@ -29,7 +29,7 @@ pub enum CoroutineState<Y, R> {
|
||||
|
||||
/// The trait implemented by builtin coroutine types.
|
||||
///
|
||||
/// Coroutines, also commonly referred to as coroutines, are currently an
|
||||
/// Coroutines are currently an
|
||||
/// experimental language feature in Rust. Added in [RFC 2033] coroutines are
|
||||
/// currently intended to primarily provide a building block for async/await
|
||||
/// syntax but will likely extend to also providing an ergonomic definition for
|
||||
|
@ -18,7 +18,7 @@ Coroutines are an extra-unstable feature in the compiler right now. Added in
|
||||
[RFC 2033] they're mostly intended right now as a information/constraint
|
||||
gathering phase. The intent is that experimentation can happen on the nightly
|
||||
compiler before actual stabilization. A further RFC will be required to
|
||||
stabilize coroutines/coroutines and will likely contain at least a few small
|
||||
stabilize coroutines and will likely contain at least a few small
|
||||
tweaks to the overall design.
|
||||
|
||||
[RFC 2033]: https://github.com/rust-lang/rfcs/pull/2033
|
||||
|
Loading…
Reference in New Issue
Block a user