-
Notifications
You must be signed in to change notification settings - Fork 13k
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 cfg_attribute_in_where #115590
Comments
Is anyone working on this or is any help needed? |
Help would certainly be welcome! |
Oh, great, I can start working on this very soon (sorry for the delayed reply btw). I'm assuming I should just ask on Zulip if I get stuck on anything? |
…=<try> Refactor `where` predicates, and reserve for attributes support Refactor `WherePredicate` to `WherePredicateKind`, and reserve for attributes support in `where` predicates. This is a part of rust-lang#115590 and is split from rust-lang#132388. r? petrochenkov
…=cjgillot Refactor `where` predicates, and reserve for attributes support Refactor `WherePredicate` to `WherePredicateKind`, and reserve for attributes support in `where` predicates. This is a part of rust-lang#115590 and is split from rust-lang#132388. r? petrochenkov
Wanted to link these here for ongoing work on adding opportunities to use cfg attributes in more places. rust-lang/rfcs#3532 -- RFC: Allow cfg-attributes on elements of tuple type #declarations |
This is a tracking issue for the RFC "Allow cfg-attributes in where clauses" (rust-lang/rfcs#3399).
The feature gate for the issue is
#![feature(cfg_attribute_in_where)]
.The intent, as described in the Guide-level explanation, is to enable cfg-attributes on where-clauses, like so:
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
Unresolved Questions
Implementation history
The text was updated successfully, but these errors were encountered: