eb3c611e1d
The very point of compile_error! is to never be reached, and one of the use cases of the macro, currently also listed as examples in the documentation of compile_error, is to create nicer errors for wrong macro invocations. Thus, we shuuld never warn about unused macro arms that contain invocations of compile_error.
54 lines
1.2 KiB
Rust
54 lines
1.2 KiB
Rust
#![allow(rustc::potential_query_instability)]
|
|
#![feature(array_windows)]
|
|
#![feature(associated_type_bounds)]
|
|
#![feature(associated_type_defaults)]
|
|
#![feature(if_let_guard)]
|
|
#![feature(let_chains)]
|
|
#![feature(let_else)]
|
|
#![feature(macro_metavar_expr)]
|
|
#![feature(proc_macro_diagnostic)]
|
|
#![feature(proc_macro_internals)]
|
|
#![feature(proc_macro_span)]
|
|
#![feature(try_blocks)]
|
|
#![recursion_limit = "256"]
|
|
|
|
#[macro_use]
|
|
extern crate rustc_macros;
|
|
|
|
extern crate proc_macro as pm;
|
|
|
|
mod placeholders;
|
|
mod proc_macro_server;
|
|
|
|
pub use mbe::macro_rules::compile_declarative_macro;
|
|
pub(crate) use rustc_span::hygiene;
|
|
pub mod base;
|
|
pub mod build;
|
|
#[macro_use]
|
|
pub mod config;
|
|
pub mod expand;
|
|
pub mod module;
|
|
pub mod proc_macro;
|
|
|
|
pub(crate) mod mbe;
|
|
|
|
// HACK(Centril, #64197): These shouldn't really be here.
|
|
// Rather, they should be with their respective modules which are defined in other crates.
|
|
// However, since for now constructing a `ParseSess` sorta requires `config` from this crate,
|
|
// these tests will need to live here in the interim.
|
|
|
|
#[cfg(test)]
|
|
mod tests;
|
|
#[cfg(test)]
|
|
mod parse {
|
|
mod tests;
|
|
}
|
|
#[cfg(test)]
|
|
mod tokenstream {
|
|
mod tests;
|
|
}
|
|
#[cfg(test)]
|
|
mod mut_visit {
|
|
mod tests;
|
|
}
|