diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-04-18 05:16:28 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-18 05:16:28 +0200 |
| commit | e15cf92b670d48cc67e36795edbf780e92d7be71 (patch) | |
| tree | d2d7b2a0517dc3a63932064120bf25d54a14bce5 /compiler/rustc_builtin_macros/src/deriving/generic/mod.rs | |
| parent | c8a9095f0f57f7a482aed4e464ec284e8f98b37b (diff) | |
| parent | 8c50f95cf088c6ccf882a152bd46c090efa3a1c7 (diff) | |
| download | rust-e15cf92b670d48cc67e36795edbf780e92d7be71.tar.gz rust-e15cf92b670d48cc67e36795edbf780e92d7be71.zip | |
Rollup merge of #139393 - willglynn:rustdoc_output_target_feature_information, r=aDotInTheVoid
rustdoc-json: Output target feature information `#[target_feature]` attributes refer to a target-specific list of features. Enabling certain features can imply enabling other features. Certain features are always enabled on certain targets, since they are required by the target's ABI. Features can also be enabled indirectly based on other compiler flags. Feature information is ultimately known to `rustc`. Rather than force external tools to track it – which may be wildly impractical due to `-C target-cpu` – have `rustdoc` output `rustc`'s feature data. This change is motivated by https://github.com/obi1kenobi/cargo-semver-checks/issues/1246, which intends to detect semver hazards caused by `#[target_feature]`. try-job: aarch64-gnu try-job: armhf-gnu try-job: test-various try-job: x86_64-msvc-1 try-job: i686-msvc-1 try-job: x86_64-mingw-1 try-job: aarch64-apple
Diffstat (limited to 'compiler/rustc_builtin_macros/src/deriving/generic/mod.rs')
0 files changed, 0 insertions, 0 deletions