rust/compiler/rustc_attr/src/lib.rs

//! Functions and types dealing with attributes and meta items.
//!
//! FIXME(Centril): For now being, much of the logic is still in `rustc_ast::attr`.
//! The goal is to move the definition of `MetaItem` and things that don't need to be in `syntax`
//! to this crate.

// tidy-alphabetical-start
#![allow(internal_features)]
#![doc(rust_logo)]
#![feature(let_chains)]
#![feature(rustdoc_internals)]
// tidy-alphabetical-end

mod builtin;
mod session_diagnostics;

pub use builtin::*;
pub use IntType::*;
pub use ReprAttr::*;
pub use StabilityLevel::*;

pub use rustc_ast::attr::*;

pub(crate) use rustc_session::HashStableContext;

rustc_fluent_macro::fluent_messages! { "../messages.ftl" }
Move builtin attribute logic to new rustc_attr crate. For now, this is all the crate contains, but more attribute logic & types will be moved there over time. 2020-01-11 12:15:20 +00:00			`//! Functions and types dealing with attributes and meta items.`
			`//!`
Rename `syntax` to `rustc_ast` in source code 2020-02-29 17:37:32 +00:00			//! FIXME(Centril): For now being, much of the logic is still in `rustc_ast::attr`.
Move builtin attribute logic to new rustc_attr crate. For now, this is all the crate contains, but more attribute logic & types will be moved there over time. 2020-01-11 12:15:20 +00:00			//! The goal is to move the definition of `MetaItem` and things that don't need to be in `syntax`
			`//! to this crate.`

Use `tidy` to sort crate attributes for all compiler crates. 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`). 2024-06-12 03:49:36 +00:00			`// tidy-alphabetical-start`
Bump cfg(bootstrap)s 2023-11-13 12:39:17 +00:00			`#![allow(internal_features)]`
			`#![doc(rust_logo)]`
Revert let_chains stabilization This reverts commit 326646074940222d602f3683d0559088690830f4. This is the revert against master, the beta revert was already done in #100538. 2022-08-20 18:40:08 +00:00			`#![feature(let_chains)]`
Use `tidy` to sort crate attributes for all compiler crates. 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`). 2024-06-12 03:49:36 +00:00			`#![feature(rustdoc_internals)]`
			`// tidy-alphabetical-end`
More let_else adoptions 2022-02-02 11:45:20 +00:00
Move builtin attribute logic to new rustc_attr crate. For now, this is all the crate contains, but more attribute logic & types will be moved there over time. 2020-01-11 12:15:20 +00:00			`mod builtin;`
Refactor diagnostics in `handle_errors` function 2022-08-21 06:46:05 +00:00			`mod session_diagnostics;`
Move builtin attribute logic to new rustc_attr crate. For now, this is all the crate contains, but more attribute logic & types will be moved there over time. 2020-01-11 12:15:20 +00:00
			`pub use builtin::*;`
			`pub use IntType::*;`
			`pub use ReprAttr::*;`
			`pub use StabilityLevel::*;`

Rename `syntax` to `rustc_ast` in source code 2020-02-29 17:37:32 +00:00			`pub use rustc_ast::attr::*;`
Move builtin attribute logic to new rustc_attr crate. For now, this is all the crate contains, but more attribute logic & types will be moved there over time. 2020-01-11 12:15:20 +00:00
Parse rustc version at compile time 2023-10-27 00:18:21 +00:00			`pub(crate) use rustc_session::HashStableContext;`
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com> 2022-10-13 09:13:02 +00:00
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter. 2023-11-21 22:53:07 +00:00			`rustc_fluent_macro::fluent_messages! { "../messages.ftl" }`