diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-02-10 13:12:31 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-10 13:12:31 +0100 |
| commit | ed3b049a8b234180f2e156dac358af4effb35f09 (patch) | |
| tree | c3334ad5f29d328dbc173d01f7d9dbc69979a281 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 9a8958f2bb9e2a9f7440226c23213725b4d777fa (diff) | |
| parent | cf1096eb72e93eeaaed2c8117d68b5798928330b (diff) | |
| download | rust-ed3b049a8b234180f2e156dac358af4effb35f09.tar.gz rust-ed3b049a8b234180f2e156dac358af4effb35f09.zip | |
Rollup merge of #120866 - Zalathar:no-min-spec, r=compiler-errors
Remove unnecessary `#![feature(min_specialization)]` As of #119963 and #120676, we can now rely on `newtype_index!` having `#[allow_internal_unstable(min_specialization)]`, so there are a few compiler crates that no longer need to include min-spec in their own crate features. --- Some of the expansions of `newtype_index!` still appear to require min-spec in the crate features. I think this is because `#[orderable]` causes the expansion to include an implementation of `TrustedStep`, which is flagged with `#[rustc_specialization_trait]`, and for whatever reason that isn't permitted by allow-internal-unstable. So this PR only touches the crates where that isn't the case.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions