Dylan DPC c1d4003506 Rollup merge of #101189 - daxpedda:ready-into-inner, r=joshtriplett ... Implement `Ready::into_inner()` Tracking issue: #101196. This implements a method to unwrap the value inside a `Ready` outside an async context. See https://docs.rs/futures/0.3.24/futures/future/struct.Ready.html#method.into_inner for previous work. This was discussed in [Zulip beforehand](https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/.60Ready.3A.3Ainto_inner.28.29.60): > An example I'm hitting right now: I have a cross-platform library that provides a functions that returns a `Future`. The only reason why it returns a `Future` is because the WASM platform requires it, but the native doesn't, to make a cross-platform API that is equal for all I just return a `Ready` on the native targets. > > Now I would like to expose native-only functions that aren't async, that users can use to avoid having to deal with async when they are targeting native. With `into_inner` that's easily solvable now. > > I want to point out that some internal restructuring could be used to solve that problem too, but in this case it's not that simple, the library uses internal traits that return the `Future` already and playing around with that would introduce unnecessary `cfg` in a lot more places. So it is really only a quality-of-life feature.		2022-10-04 16:11:00 +05:30
..
benches	Use internal iteration in Iterator::{cmp_by, partial_cmp_by, eq_by}	2022-08-21 12:23:10 +02:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Rollup merge of #101189 - daxpedda:ready-into-inner, r=joshtriplett	2022-10-04 16:11:00 +05:30
tests	Rollup merge of #101308 - nerdypepper:feature/is-ascii-octdigit, r=joshtriplett	2022-10-03 20:58:56 +02:00
Cargo.toml	Avoid use of rand::thread_rng in stdlib benchmarks	2022-05-02 00:08:21 -07:00