Tracking Issue for `async {}` blocks in const expressions

[jonas-schievink]

This is a tracking issue for use of async {} expressions in const contexts.
The feature gate for the issue is #![feature(const_async_blocks)].

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 (Allow async {} expressions in const contexts #85353)
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

Implementation history

[CryZe]

Technically this already existed, but I'll close mine in favor of this one: #69431

[jonas-schievink]

Ah okay, normally we don't have tracking issues for things that aren't implemented

[Swatinem]

Hi! 👋🏻
I discovered while working on #104321 that async blocks can trivially be const as soon as the #104826 workaround is fixed.

Depending on whats happening with #104826, what would be the next steps in moving forward with the feature flag/stabilization?

[CryZe]

Is there anything preventing this from getting stabilized? I'd like to do the remaining work to push this to stabilization.