75b164d836
We already do this for a number of crates, e.g. `rustc_middle`, `rustc_span`, `rustc_metadata`, `rustc_span`, `rustc_errors`. For the ones we don't, in many cases the attributes are a mess. - There is no consistency about order of attribute kinds (e.g. `allow`/`deny`/`feature`). - Within attribute kind groups (e.g. the `feature` attributes), sometimes the order is alphabetical, and sometimes there is no particular order. - Sometimes the attributes of a particular kind aren't even grouped all together, e.g. there might be a `feature`, then an `allow`, then another `feature`. This commit extends the existing sorting to all compiler crates, increasing consistency. If any new attribute line is added there is now only one place it can go -- no need for arbitrary decisions. Exceptions: - `rustc_log`, `rustc_next_trait_solver` and `rustc_type_ir_macros`, because they have no crate attributes. - `rustc_codegen_gcc`, because it's quasi-external to rustc (e.g. it's ignored in `rustfmt.toml`).
23 lines
682 B
Rust
23 lines
682 B
Rust
//! The `rustc_ast_passes` crate contains passes which validate the AST in `syntax`
|
|
//! parsed by `rustc_parse` and then lowered, after the passes in this crate,
|
|
//! by `rustc_ast_lowering`.
|
|
//!
|
|
//! The crate also contains other misc AST visitors, e.g. `node_count` and `show_span`.
|
|
|
|
// tidy-alphabetical-start
|
|
#![allow(internal_features)]
|
|
#![doc(rust_logo)]
|
|
#![feature(box_patterns)]
|
|
#![feature(if_let_guard)]
|
|
#![feature(iter_is_partitioned)]
|
|
#![feature(let_chains)]
|
|
#![feature(rustdoc_internals)]
|
|
// tidy-alphabetical-end
|
|
|
|
pub mod ast_validation;
|
|
mod errors;
|
|
pub mod feature_gate;
|
|
pub mod node_count;
|
|
pub mod show_span;
|
|
|
|
rustc_fluent_macro::fluent_messages! { "../messages.ftl" }
|