Open
Description
This is a tracking issue for the super let
experiment.
The feature gate for the issue is #![feature(super_let)]
.
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used 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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps / History
- Accept lang experiment.
- Implement
super let
- Clean up / simplify rustc_hir_analysis::check::region to make
super let
implementation easier - Implement
super let
#139112
- Clean up / simplify rustc_hir_analysis::check::region to make
- Use
super let
inpin!()
- Use
super let
informat_args!()
- ...
- Consider other syntaxes/solutions
- ...
- Write an RFC?
- Get the RFC accepted
- ...
- Adjust documentation (see instructions on rustc-dev-guide)
- Formatting for new syntax has been added to the Style Guide (nightly-style-procedure)
- Stabilization PR (see instructions on rustc-dev-guide)
Unresolved Questions
- What are the exact rules for
super let
? super let x;
without initializer?super let _ = _ else { _ };
?super let
at function body scope?- Best syntax for this feature?
Metadata
Metadata
Assignees
Labels
Blocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize).Blocker: Implemented in the nightly compiler and unstable.Category: An issue tracking the progress of sth. like the implementation of an RFCStatus: There are blocking design concerns.Relevant to the language team, which will review and decide on the PR/issue.