diff options
| author | bors <bors@rust-lang.org> | 2020-09-12 02:13:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-09-12 02:13:28 +0000 |
| commit | 94a7ea271f0996848f8fa03c61067620736b1242 (patch) | |
| tree | 91282cf4ea03e9e4369f6e43c9e3823ae8c24534 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 12c10e34a49385d329e15575027d0faa729986f3 (diff) | |
| parent | 688f4471fd553c83ae3ff0306956d89b7d7c2d28 (diff) | |
| download | rust-94a7ea271f0996848f8fa03c61067620736b1242.tar.gz rust-94a7ea271f0996848f8fa03c61067620736b1242.zip | |
Auto merge of #74328 - yoshuawuyts:stabilize-future-readiness-fns, r=sfackler
Stabilize core::future::{pending,ready}
This PR stabilizes `core::future::{pending,ready}`, tracking issue https://github.com/rust-lang/rust/issues/70921.
## Motivation
These functions have been on nightly for three months now, and have lived as part of the futures ecosystem for several years. In that time these functions have undergone several iterations, with [the `async-std` impls](https://docs.rs/async-std/1.6.2/async_std/future/index.html) probably diverging the most (using `async fn`, which in hindsight was a mistake).
It seems the space around these functions has been _thoroughly_ explored over the last couple of years, and the ecosystem has settled on the current shape of the functions. It seems highly unlikely we'd want to make any further changes to these functions, so I propose we stabilize.
## Implementation notes
This stabilization PR was fairly straightforward; this feature has already thoroughly been reviewed by the libs team already in https://github.com/rust-lang/rust/pull/70834. So all this PR does is remove the feature gate.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions