bors bca5fdebe0 Auto merge of #131321 - RalfJung:feature-activation, r=nnethercote ... terminology: #[feature] *enables* a feature (instead of "declaring" or "activating" it) Mostly, we currently call a feature that has a corresponding `#[feature(name)]` attribute in the current crate a "declared" feature. I think that is confusing as it does not align with what "declaring" usually means. Furthermore, we *also* refer to `#[stable]`/`#[unstable]` as *declaring* a feature (e.g. in [these diagnostics](f25e5abea2/compiler/rustc_passes/messages.ftl (L297-L301))), which aligns better with what "declaring" usually means. To make things worse, the functions `tcx.features().active(...)` and `tcx.features().declared(...)` both exist and they are doing almost the same thing (testing whether a corresponding `#[feature(name)]` exists) except that `active` would ICE if the feature is not an unstable lang feature. On top of this, the callback when a feature is activated/declared is called `set_enabled`, and many comments also talk about "enabling" a feature. So really, our terminology is just a mess. I would suggest we use "declaring a feature" for saying that something is/was guarded by a feature (e.g. `#[stable]`/`#[unstable]`), and "enabling a feature" for `#[feature(name)]`. This PR implements that.		2024-10-22 11:02:35 +00:00
..
assembly	Rollup merge of #131807 - beetrees:riscv-target-abi, r=workingjubilee	2024-10-21 20:32:01 -07:00
auxiliary
codegen	Rollup merge of #131807 - beetrees:riscv-target-abi, r=workingjubilee	2024-10-21 20:32:01 -07:00
codegen-units
coverage	Dont ICE when computing coverage of synthetic async closure body	2024-10-18 20:14:02 +11:00
coverage-run-rustdoc
crashes	Rollup merge of #131964 - matthiaskrgr:crashes2010, r=jieyouxu	2024-10-20 16:54:12 +02:00
debuginfo	Auto merge of #131570 - ehuss:update-xcode, r=Mark-Simulacrum	2024-10-21 20:19:06 +00:00
incremental	Bless incremental tests.	2024-10-04 23:50:01 +00:00
mir-opt	Rollup merge of #130350 - RalfJung:strict-provenance, r=dtolnay	2024-10-21 18:11:19 +02:00
pretty	Add pretty, ui, and feature-gate tests for the enzyme/autodiff frontend	2024-10-11 20:38:43 +02:00
run-make	Add rustc_abi and rustc_parse_format to rustc-crates-on-stable test	2024-10-21 14:57:41 +02:00
rustdoc	Dont consider predicates that may hold as impossible in is_impossible_associated_item	2024-10-17 12:32:31 -04:00
rustdoc-gui	Strengthen some GUI tests	2024-10-09 21:23:20 +02:00
rustdoc-js
rustdoc-js-std	Fix rustdoc-js-std path-ordering test due to API removal	2024-10-02 11:15:48 +02:00
rustdoc-json	rustdoc-JSON: Rename "object safe" to "dyn compatible"	2024-10-16 23:00:49 +02:00
rustdoc-ui	terminology: #[feature] *enables* a feature (instead of "declaring" or "activating" it)	2024-10-22 07:37:54 +01:00
ui	Auto merge of #131321 - RalfJung:feature-activation, r=nnethercote	2024-10-22 11:02:35 +00:00
ui-fulldeps	update bootstrap configs	2024-10-15 20:30:23 -07:00
COMPILER_TESTS.md