-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Add tidy-alphabetical-start/end around feature lists and, in some cases, allow/warn/deny lists #114766
Add tidy-alphabetical-start/end around feature lists and, in some cases, allow/warn/deny lists #114766
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,10 @@ | ||
#![feature(rustc_private)] | ||
// Note: please avoid adding other feature gates where possible | ||
#![feature(rustc_private)] | ||
// tidy-alphabetical-start | ||
#![warn(rust_2018_idioms)] | ||
#![warn(unused_lifetimes)] | ||
#![warn(unreachable_pub)] | ||
#![warn(unused_lifetimes)] | ||
// tidy-alphabetical-end | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you please skip this for cg_clif? There is nothing in place in https://github.com/bjorn3/rustc_codegen_cranelift to enforce this and because of this it will only cause issues when syncing between that repo and this repo. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same applies to rust-analyzer, I'd say this should not be done for subtrees in general. |
||
|
||
extern crate jobserver; | ||
#[macro_use] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment was intentionally before the feature gate as you did likely add new feature gates after the last one, which is exactly where the comment is positioned.