Will Glynn

We could add retrospective support on best-effort basis by shipping target feature data extracted from current nightly. Concretely, [these feature lists](https://gist.github.com/willglynn/97f4b934ffaa3e8269e1fa2a0c251b50) are probably applicable to 1.86, and to the extent...

I started backporting at 1.84.0 just to see what that would look like. It is indeed entirely practical. ```console % git checkout rustdoc_target_features_backport_v1.84.0 % git restore --recurse-submodules library/backtrace library/stdarch %...

That repo presently contains 1658 JSON files covering 291 targets, but only… 189 unique `target_features` arrays. Basic deduplication goes a long ways, and clever-er deduplication would go even further. What...

I now have a crate which provides that interface. It's pure Rust, it's `#![forbid(unsafe_code)]`, it has no `[dependencies]`, and the tests say it returns output identical to all 2128 JSON...

I published [`rust-target-feature-data`](https://crates.io/crates/rust-target-feature-data) 0.1.0 ([docs](https://docs.rs/rust-target-feature-data/0.1.0)) containing Rust 1.83.0–1.87.0 target feature data. Seems like I should maybe drop 1.83.0 now? As a curiosity, I continued backporting a bit. This approach hits...

I agree, but I wonder: does this matter? `cargo build` and `cargo check` both fail on such functions: ``` Checking playground v0.0.1 (/playground) error: the feature named `leoncasa` is not...

A requirement we [identified early](https://github.com/obi1kenobi/cargo-semver-checks/issues/1246#issuecomment-2778738518) was that these lints require running `cargo-semver-checks` for each relevant target: > > It seems unfortunate that `#[target_feature]` use imposes a requirement to evaluate these...

Thanks for this project! It's been a pleasure to use and was a significant factor in my decision to purchase Samsung products.