Skip to content
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

Tracking Issue for for-loops in constants #87575

Open
jonas-schievink opened this issue Jul 29, 2021 · 7 comments
Open

Tracking Issue for for-loops in constants #87575

jonas-schievink opened this issue Jul 29, 2021 · 7 comments
Labels
A-const-fn Area: const fn foo(..) {..}. Pure functions which can be applied at compile time. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature.

Comments

@jonas-schievink
Copy link
Contributor

This tracks #![feature(const_for)], added in #87237.

This feature depends on const_trait_impl and is not currently usable.

@jonas-schievink jonas-schievink added A-const-fn Area: const fn foo(..) {..}. Pure functions which can be applied at compile time. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. labels Jul 29, 2021
@SUPERCILEX
Copy link
Contributor

Is there a tracking issue for const range iterators? Doing something like for i in 0..1000 { doesn't compile... am I missing something?

@CalinZBaenen

This comment was marked as off-topic.

@mati865

This comment was marked as off-topic.

@CalinZBaenen

This comment was marked as off-topic.

@mati865

This comment was marked as off-topic.

@CalinZBaenen

This comment was marked as off-topic.

@Tom1380

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-const-fn Area: const fn foo(..) {..}. Pure functions which can be applied at compile time. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature.
Projects
None yet
Development

No branches or pull requests

5 participants