Tracking Issue for closures in const contexts

[fee1-dead]

This is a tracking issue for declaring const closures.
The feature gate for the issue is #![feature(const_closures)].

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.

Steps

• Implement the feature (Const closures #106004)
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• for<'a> const static async move || {} (keyword order?)

Implementation history

[Jerrody]

Unresolved Questions

• const static async move || {} (keyword order?)

In my opinion, suggested keyword order is good.

[dtolnay]

Unresolved Questions

• for<'a> const static async move || {} (keyword order?)

Data point: const async fn f() {} is the order accepted for function definitions, so we should ensure at minimum the relative order of const–async is consistent.

[jhpratt]

For the top-level comment: the feature is #![feature(const_closures)], plural.