rust/compiler/rustc_feature/src/lib.rs, branch 1.75.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.75.02023-10-16T22:38:08+00:00docs: add Rust logo to more compiler crates2023-10-16T22:38:08+00:00Michael Howellmichael@notriddle.com2023-10-16T22:22:17+00:00urn:sha1:2ff2624722a8e0022ba0783d5870456df379ed94
c6e6ecb1afea9695a42d0f148ce153536b279eb5 added it to some of the
compiler's crates, but avoided adding it to all of them to reduce
bit-rot. This commit adds to more.
Rename `ACTIVE_FEATURES` as `UNSTABLE_FEATURES`.2023-10-15T21:17:23+00:00Nicholas Nethercoten.nethercote@gmail.com2023-10-05T08:43:35+00:00urn:sha1:d284c8a2d7a2de918a966bee9c9069d7b5bf06bf
It's a better name, and lets "active features" refer to the features
that are active in a particular program, due to being declared or
enabled by the edition.
The commit also renames `Features::enabled` as `Features::active` to
match this; I changed my mind and have decided that "active" is a little
better thatn "enabled" for this, particularly because a number of
pre-existing comments use "active" in this way.
Finally, the commit renames `Status::Stable` as `Status::Accepted`, to
match `ACCEPTED_FEATURES`.
Remove `rustc_feature::State`.2023-10-15T21:15:30+00:00Nicholas Nethercoten.nethercote@gmail.com2023-10-05T07:59:01+00:00urn:sha1:41b689948736cc79f35b6002c040513291dcd7c2
`State` is used to distinguish active vs accepted vs removed features.
However, these can also be distinguished by their location, in
`ACTIVE_FEATURES`, `ACCEPTED_FEATURES`, and `REMOVED_FEATURES`.
So this commit removes `State` and moves the internals of its variants
next to the `Feature` in each element of `*_FEATURES`, introducing new
types `ActiveFeature` and `RemovedFeature`. (There is no need for
`AcceptedFeature` because `State::Accepted` had no fields.)
This is a tighter type representation, avoids the need for some runtime
checks, and makes the code a bit shorter.
Merge `STABLE_REMOVED_FEATURES` list into `REMOVED_FEATURES`.2023-10-05T00:42:32+00:00Nicholas Nethercoten.nethercote@gmail.com2023-10-05T00:38:43+00:00urn:sha1:8ba91378401f5483b1d834be33911028507a9d5d
There is a single features (`no_stack_check`) in
`STABLE_REMOVED_FEATURES`. But the treatment of
`STABLE_REMOVED_FEATURES` and `REMOVED_FEATURES` is actually identical.
So this commit just merges them, and uses a comment to record
`no_stack_check`'s unique "stable removed" status.
This also lets `State::Stabilized` (which was a terrible name) be
removed.
Streamline `find_lang_feature_issue`.2023-10-04T23:23:26+00:00Nicholas Nethercoten.nethercote@gmail.com2023-10-04T03:54:12+00:00urn:sha1:1ddb2872ddeb5d56f7bdecfd4175fb13fc510069
It currently processes `ACTIVE_FEATURES` separately from
`ACCEPTED_FEATURES`, `REMOVED_FEATURES`, and `STABLE_REMOVED_FEATURES`,
for no good reason. This commit treats them uniformly.
Remove unused `Span` from the `set` function in `State::Active`.2023-10-04T23:18:29+00:00Nicholas Nethercoten.nethercote@gmail.com2023-10-03T22:51:03+00:00urn:sha1:53fe37de2e11537bf2953a29df3c5be8a8858850Issue numbers are enforced on active features; remove FIXME2023-08-06T18:01:23+00:00Martin Nordholtsenselic@gmail.com2023-08-06T17:55:28+00:00urn:sha1:2b9876bd6da460b4748627567c9cd1dfb1f97030Use `is_some_and`/`is_ok_and` in less obvious spots2023-05-24T14:33:43+00:00Maybe Wafflewaffle.lapkin@gmail.com2023-05-24T14:33:43+00:00urn:sha1:307799a711826294bc2b3e562cd87bf1e2ff28b4Use `Option::is_some_and` and `Result::is_ok_and` in the compiler2023-05-24T14:20:41+00:00Maybe Wafflewaffle.lapkin@gmail.com2023-05-24T14:19:22+00:00urn:sha1:fb0f74a8c9e8b8f488ec5894d5d314caebf4c662Stabilize a portion of 'once_cell'2023-03-29T22:04:44+00:00Trevor Grosstmgross@umich.edu2022-12-12T05:42:45+00:00urn:sha1:dc4ba57566acac492df2c2074d2d7144566dc7df
Move items not part of this stabilization to 'lazy_cell' or 'once_cell_try'