| Age | Commit message (Collapse) | Author | Lines |
|---|
|
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`).
|
|
|
|
We are not planning to support user generated constant in the
foreseeable future, so we are removing the Fold logic for now in
favor of the Instance::resolve logic.
The Instance::resolve was however incomplete, since we weren't handling
internalizing constants yet. Thus, I added that.
I decided to keep the Const fields private in case we decide to
translate them lazily.
|
|
|
|
|
|
usage of forever unstable things
|
|
|
|
|
|
- Introduce an Opaque type for adding information that is still
internal to the compiler.
|
|
Add extern declarations and optional dependencies to fix build done
directly via `cargo build`.
|
|
|
|
|
|
+ Add some information to the README.md
|
|
This approach didn't seem to work well.
|
|
|
|
|
|
'9abcb5c7b574cf316eb23d3f469187bb86ba3019'
git-subtree-dir: compiler/rustc_smir
git-subtree-mainline: fb1976011e3df96b5d3eccd6b2f4e51ef7dc8f16
git-subtree-split: 9abcb5c7b574cf316eb23d3f469187bb86ba3019
|
