mirror of
https://github.com/rust-lang/rust.git
synced 2025-06-22 12:37:32 +00:00
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`).
29 lines
832 B
Rust
29 lines
832 B
Rust
//! Queries that are independent from the main solver code.
|
|
|
|
// tidy-alphabetical-start
|
|
#![recursion_limit = "256"]
|
|
// tidy-alphabetical-end
|
|
|
|
mod codegen;
|
|
mod dropck_outlives;
|
|
mod evaluate_obligation;
|
|
mod implied_outlives_bounds;
|
|
mod normalize_erasing_regions;
|
|
mod normalize_projection_ty;
|
|
mod type_op;
|
|
|
|
pub use rustc_trait_selection::traits::query::type_op::ascribe_user_type::type_op_ascribe_user_type_with_span;
|
|
pub use type_op::type_op_prove_predicate_with_cause;
|
|
|
|
use rustc_middle::query::Providers;
|
|
|
|
pub fn provide(p: &mut Providers) {
|
|
dropck_outlives::provide(p);
|
|
evaluate_obligation::provide(p);
|
|
implied_outlives_bounds::provide(p);
|
|
normalize_projection_ty::provide(p);
|
|
normalize_erasing_regions::provide(p);
|
|
type_op::provide(p);
|
|
p.codegen_select_candidate = codegen::codegen_select_candidate;
|
|
}
|