rust/compiler/rustc_feature/src/lib.rs, branch 1.83.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.83.02024-09-22T23:11:29+00:00Reformat using the new identifier sorting from rustfmt2024-09-22T23:11:29+00:00Michael Gouletmichael@errs.io2024-09-22T23:05:04+00:00urn:sha1:c682aa162b0d41e21cc6748f4fecfe01efb69d1fCorrectly handle stability of `#[diagnostic]` attributes2024-09-06T17:01:45+00:00Georg Semmlergithub@weiznich.de2024-09-06T16:47:22+00:00urn:sha1:717a11788d49a960c94509ec97d35114fa4b3a7f
This commit changes the way we treat the stability of attributes in the
`#[diagnostic]` namespace. Instead of relaying on ad-hoc checks to
ensure at call side that a certain attribute is really usable at that
location it centralises the logic to one place. For diagnostic
attributes comming from other crates it just skips serializing
attributes that are not stable and that do not have the corresponding
feature enabled. For attributes from the current crate we can just use
the feature information provided by `TyCtx`.
Add `warn(unreachable_pub)` to `rustc_feature`.2024-08-27T02:55:54+00:00Nicholas Nethercoten.nethercote@gmail.com2024-08-27T02:55:54+00:00urn:sha1:0d8d05c07f8be4c90adf27141c0f64f76c318f64Reformat `use` declarations.2024-07-28T22:26:52+00:00Nicholas Nethercoten.nethercote@gmail.com2024-07-28T22:13:50+00:00urn:sha1:84ac80f1921afc243d71fd0caaa4f2838c294102
The previous commit updated `rustfmt.toml` appropriately. This commit is
the outcome of running `x fmt --all` with the new formatting options.
clarify the meaning of the version number for accepted/removed features2024-07-14T06:18:03+00:00Ralf Jungpost@ralfj.de2024-07-14T06:18:03+00:00urn:sha1:2dd5369eda4337f44a8bb666bfd38b2c5e3b0fdeAdd hard error and migration lint for unsafe attrs2024-06-24T00:02:14+00:00carbotaniuman41451839+carbotaniuman@users.noreply.github.com2024-06-08T23:39:09+00:00urn:sha1:a23917cfd07b309f32603c6acb81b63aad8504e7Use `tidy` to sort crate attributes for all compiler crates.2024-06-12T05:49:10+00:00Nicholas Nethercoten.nethercote@gmail.com2024-06-12T03:49:36+00:00urn:sha1:75b164d836ff82b459dfb05646bf0328dd23d2fd
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`).
Error on unsafe on non-unsafe attribute2024-06-07T01:26:28+00:00carbotaniuman41451839+carbotaniuman@users.noreply.github.com2024-05-15T23:52:08+00:00urn:sha1:230b58febf78bb1680b4960d32350a7430a8aab5Stabilize `LazyCell` and `LazyLock` (`lazy_cell`)2024-02-21T03:55:13+00:00Peter Jaszkowiakp.jaszkow@gmail.com2024-02-21T03:55:13+00:00urn:sha1:4913ab8f779582dc9da099a148a4670ede0e15aaStabilize generic `NonZero`.2024-04-22T16:48:47+00:00Markus Reiterme@reitermark.us2024-04-21T16:41:45+00:00urn:sha1:33e68aadc975c60bf975789f70156e67082e8910