Repository navigation
Tracking Issue for future readiness functions #70921
Description
Activity
Currently we have:
pub struct Pending<T> { _data: marker::PhantomData<T>, }
That means
Pending<T>has dropcheck behavior as though it owns aTvalue, which it doesn't. Should we instead change it to:pub struct Pending<T> { _data: marker::PhantomData<fn() -> T>, }
I believe that is a strict improvement without any compatibility issues, as the variance is the same.
@petertodd this was discussed in #70834 and decided against. Some of the conversation happened in code comments, so it may require expanding some closed comments to get the full conversation.
With the release of 1.48 these PRs have been stabilized, so it's probably time to close! Any conversation about these APIs should probably happen in their own PRs.
- Thanks for the reply! I missed those comments. Anyway, too small a difference to worry about now if it's already been discussed.…On November 19, 2020 4:43:13 PM EST, Yoshua Wuyts ***@***.***> wrote: @petertodd this was discussed in #70834 and decided against. Some of the conversation happened in code comments, so it may require expanding some closed comments to get the full conversation. With the release of 1.48 these PRs have been stabilized, so it's probably time to close! Any conversation about these APIs should probably happen in their own PRs. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #70921 (comment)
This is a tracking issue for
core::future::{pending,ready}.The feature gate for the issue is
#![feature(future_readiness_fns)].About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Unresolved Questions
Implementation history