rust/compiler/rustc_interface/src/lib.rs

// tidy-alphabetical-start
#![feature(decl_macro)]
#![feature(file_buffered)]
#![feature(iter_intersperse)]
#![feature(let_chains)]
#![feature(try_blocks)]
#![warn(unreachable_pub)]
// tidy-alphabetical-end

mod callbacks;
mod errors;
pub mod interface;
pub mod passes;
mod proc_macro_decls;
mod queries;
pub mod util;

pub use callbacks::setup_callbacks;
pub use interface::{Config, run_compiler};
pub use passes::DEFAULT_QUERY_PROVIDERS;
pub use queries::{Linker, Queries};

#[cfg(test)]
mod tests;

rustc_fluent_macro::fluent_messages! { "../messages.ftl" }
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`
Fix `rustdoc --version` when used with download-rustc Previously, rustdoc would unconditionally report the version that rustc was compiled with. That showed things like `nightly-2022-10-30`, which wasn't right, since this was a `dev` build compiled from source. Fix it by changing `rustc_driver::version` to a macro expanded at invocation time. 2022-11-09 08:52:59 +00:00			`#![feature(decl_macro)]`
Dogfood `feature(file_buffered)` 2024-09-24 21:25:16 +00:00			`#![feature(file_buffered)]`
add unstable support for outputting file checksums for use in cargo 2024-06-22 07:27:59 +00:00			`#![feature(iter_intersperse)]`
MCP636: Add simpler and more explicit syntax to check-cfg This add a new form and deprecated the other ones: - cfg(name1, ..., nameN, values("value1", "value2", ... "valueN")) - cfg(name1, ..., nameN) or cfg(name1, ..., nameN, values()) - cfg(any()) It also changes the default exhaustiveness to be enable-by-default in the presence of any --check-cfg arguments. 2023-05-01 12:17:56 +00:00			`#![feature(let_chains)]`
Don't call closures immediately, use `try{}` blocks 2023-01-09 15:15:26 +00:00			`#![feature(try_blocks)]`
Add `warn(unreachable_pub)` to `rustc_interface`. 2024-08-27 05:11:54 +00:00			`#![warn(unreachable_pub)]`
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-end`
Introduce rustc_interface and move some methods there 2018-12-08 19:30:23 +00:00
Store callbacks in global statics The callbacks have precisely two states: the default, and the one present throughout almost all of the rustc run (the filled in value which has access to TyCtxt). We used to store this as a thread local, and reset it on each thread to the non-default value. But this is somewhat wasteful, since there is no reason to set it globally -- while the callbacks themselves access TLS, they do not do so in a manner that fails in when we do not have TLS to work with. 2019-12-25 18:38:57 +00:00			`mod callbacks;`
Move existing diagnostic struct to a new errors module 2022-08-20 16:30:49 +00:00			`mod errors;`
Make the rustc driver and interface demand driven 2018-12-08 19:30:23 +00:00			`pub mod interface;`
Inline write_dep_info query 2024-06-22 09:14:26 +00:00			`pub mod passes;`
Make the rustc driver and interface demand driven 2018-12-08 19:30:23 +00:00			`mod proc_macro_decls;`
			`mod queries;`
Introduce rustc_interface and move some methods there 2018-12-08 19:30:23 +00:00			`pub mod util;`
Make the rustc driver and interface demand driven 2018-12-08 19:30:23 +00:00
Move setup_callbacks call to create_compiler_and_run This ensures that it is called even when run_in_thread_pool_with_globals is avoided and reduces code duplication between the parallel and non-parallel version of run_in_thread_pool_with_globals 2021-06-25 11:03:39 +00:00			`pub use callbacks::setup_callbacks;`
Make the rustc driver and interface demand driven 2018-12-08 19:30:23 +00:00			`pub use interface::{Config, run_compiler};`
Merge `ExternProviders` into the general `Providers` struct 2023-09-22 16:38:31 +00:00			`pub use passes::DEFAULT_QUERY_PROVIDERS;`
Move codegen_and_build_linker from Queries to Linker 2024-06-30 18:44:11 +00:00			`pub use queries::{Linker, Queries};`
move parse_cfgspecs to rustc_interface 2019-10-11 21:48:16 +00:00
			`#[cfg(test)]`
			`mod tests;`
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" }`