3 ms·

As far as I know, the proposal to add one was determined to need an RFC: https://github.com/rust-lang/rust/pull/65875 https://github.com/rust-lang/rust/pull/658

• devit 3y ago
  Another instance of a trivial and obvious feature that can only really be designed one way that is not implemented 4 years after initial proposal.
  • steveklabnik 3y ago
    I am not fully sure I agree with the first part of your assessment, but I share the frustration that a feature like this, which would be useful and is not particularly large, is basically ignored by the working group, while larger, more controversial, and less useful features, like keyword generics, are pursued while the more useful things languish.
    • Matthias247 3y ago
      As the person who proposed this feature - among lots of other ones for async Rust, like run-to-completion async functions (https://github.com/Matthias247/rfcs/blob/e7fd7042f8069e9126e2096156d2abe3c38e781b/text/0000-run-to-completion-async-fn.md https://github.com/Matthias247/rfcs/blob/e7fd7042f8069e9126e...), structured concurrency, cancellation tokens, etc) - I can unfortunately share this sentiment. It seemed really hard to land anything in async Rust since the priorities don't seem overly clear. Therefore I put a pause on all contribution attempts and went back to just using Rust as a user.