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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for using the ?-operator in constants #87576

Closed
jonas-schievink opened this issue Jul 29, 2021 · 1 comment
Closed

Tracking Issue for using the ?-operator in constants #87576

jonas-schievink opened this issue Jul 29, 2021 · 1 comment
Labels
A-const-eval Area: constant evaluation (mir interpretation) 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_try)], added in #87237.

This feature depends on const_trait_impl and is not currently usable by itself.
@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. A-const-eval Area: constant evaluation (mir interpretation) labels Jul 29, 2021
@usbalbin usbalbin mentioned this issue Jul 29, 2021
Merged
@jonas-schievink
Copy link
Contributor Author

Duplicate of #74935

@jonas-schievink jonas-schievink marked this as a duplicate of #74935 Jul 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-const-eval Area: constant evaluation (mir interpretation) 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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonas-schievink