-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unstable gen_future
Feature Tracking
#137061
Unstable gen_future
Feature Tracking
#137061
Conversation
library/core/src/future/mod.rs with issue = "none"
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ibraheemdev (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
gen_future
Feature Tracking gen_future
Feature Tracking
tidy is very fussy about formatting, please bless. |
done tiding up,
|
@workingjubilee can ask something off topic ? my local machine is kinda meh and good enough for running intellisense or linter let alone compile. i wrote a github codespace config to work on rust. should i open another pr to merge it in so others can use it to work on this using standardized config and not waste time writing a config each time anyone have to use codespace ? |
Thanks. @bors r+ rollup |
Rollup of 10 pull requests Successful merges: - rust-lang#136610 (Allow `IndexSlice` to be indexed by ranges.) - rust-lang#136991 ([rustdoc] Add new setting to wrap source code lines when too long) - rust-lang#137061 (Unstable `gen_future` Feature Tracking ) - rust-lang#137393 (Stabilize `unbounded_shifts`) - rust-lang#137482 (Windows: use existing wrappers in `File::open_native`) - rust-lang#137484 (Fix documentation for unstable sort on slice) - rust-lang#137491 (Tighten `str-to-string-128690.rs``CHECK{,-NOT}`s to make it less likely to incorrectly fail with symbol name mangling) - rust-lang#137495 (Added into_value function to ControlFlow<T, T>) - rust-lang#137501 (Move `impl` blocks out of `rustc_middle/src/mir/syntax.rs`) - rust-lang#137505 (Add a span to `CompilerBuiltinsCannotCall`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#137061 - progressive-galib:gen_future-closing#76249, r=ibraheemdev Unstable `gen_future` Feature Tracking This PR removes the reference to the closed tracking issue **rust-lang#50547** for the `gen_future` feature. Since `gen_future` is an internal feature used in async block desugaring, it does not require a public tracking issue. #### Changes: - Replaced `issue = "50547"` with `issue = "none"` in **library/core/src/future/mod.rs**. - Ensures that it is correctly identified as an internal feature. #### Rationale: With this change, the Unstable Book will now state: > *"This feature has no tracking issue and is therefore likely internal to the compiler, not being intended for general use."* Closes **rust-lang#76249**. 🚀🦀
This PR removes the reference to the closed tracking issue #50547 for the
gen_future
feature. Sincegen_future
is an internal feature used in async block desugaring, it does not require a public tracking issue.Changes:
issue = "50547"
withissue = "none"
in library/core/src/future/mod.rs.Rationale:
With this change, the Unstable Book will now state:
Closes #76249. 🚀🦀