rust-lang / rust-lang/rust

Tracking Issue for `super let`

Open
#139,076 10 comments 60 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

B-experimental B-unstable C-tracking-issue F-super_let S-tracking-design-concerns T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

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
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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the super let feature gate and the tracking checklist, then review the unresolved syntax and rule questions. Read the linked rustc-dev-guide documentation and stabilization guidance, along with the Style Guide procedure. Done requires settled semantics, an accepted RFC, updated documentation and formatting, and a stabilization PR.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.