rust/compiler/rustc_interface/src/lib.rs

#![feature(decl_macro)]
#![feature(generic_nonzero)]
#![feature(lazy_cell)]
#![feature(let_chains)]
#![feature(thread_spawn_unchecked)]
#![feature(try_blocks)]

#[macro_use]
extern crate tracing;

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

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

#[cfg(test)]
mod tests;

rustc_fluent_macro::fluent_messages! { "../messages.ftl" }
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 02:52:59 -06:00			`#![feature(decl_macro)]`
Use generic `NonZero` internally. 2024-01-29 23:59:09 +01:00			`#![feature(generic_nonzero)]`
Stabilize a portion of 'once_cell' Move items not part of this stabilization to 'lazy_cell' or 'once_cell_try' 2022-12-12 00:42:45 -05:00			`#![feature(lazy_cell)]`
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 14:17:56 +02:00			`#![feature(let_chains)]`
Format sources into the error message when loading codegen backends cc https://github.com/rust-lang/rustc_codegen_cranelift/issues/1447 2024-01-10 17:13:03 +02:00			`#![feature(thread_spawn_unchecked)]`
Don't call closures immediately, use `try{}` blocks 2023-01-09 15:15:26 +00:00			`#![feature(try_blocks)]`
Introduce rustc_interface and move some methods there 2018-12-08 20:30:23 +01:00
Always import all tracing macros for the entire crate instead of piecemeal by module 2022-08-31 13:09:26 +00:00			`#[macro_use]`
			`extern crate tracing;`

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 13:38:57 -05:00			`mod callbacks;`
Move existing diagnostic struct to a new errors module 2022-08-20 18:30:49 +02:00			`mod errors;`
Make the rustc driver and interface demand driven 2018-12-08 20:30:23 +01:00			`pub mod interface;`
			`mod passes;`
			`mod proc_macro_decls;`
			`mod queries;`
Introduce rustc_interface and move some methods there 2018-12-08 20:30:23 +01:00			`pub mod util;`
Make the rustc driver and interface demand driven 2018-12-08 20:30:23 +01: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 13:03:39 +02:00			`pub use callbacks::setup_callbacks;`
Make the rustc driver and interface demand driven 2018-12-08 20:30:23 +01:00			`pub use interface::{run_compiler, Config};`
Merge `ExternProviders` into the general `Providers` struct 2023-09-22 16:38:31 +00:00			`pub use passes::DEFAULT_QUERY_PROVIDERS;`
pass Queries to compiler callbacks 2019-11-30 10:16:19 +01:00			`pub use queries::Queries;`
move parse_cfgspecs to rustc_interface 2019-10-11 23:48:16 +02: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 10:13:02 +01: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-22 09:53:07 +11:00			`rustc_fluent_macro::fluent_messages! { "../messages.ftl" }`