diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-08-05 05:40:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-05 05:40:19 +0200 |
| commit | cc61dc8b2d97870b8bb40c01649ccc587aa8b550 (patch) | |
| tree | 9aea65fa7e76115550c56ebd037f066977d28971 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 176e5452095444815207be02c16de0b1487a1b53 (diff) | |
| parent | 9d9b55cd2b14bce066cef83d9d85ba798a2ba95c (diff) | |
| download | rust-cc61dc8b2d97870b8bb40c01649ccc587aa8b550.tar.gz rust-cc61dc8b2d97870b8bb40c01649ccc587aa8b550.zip | |
Rollup merge of #127655 - RalfJung:invalid_type_param_default, r=compiler-errors
turn `invalid_type_param_default` into a `FutureReleaseErrorReportInDeps` `````@rust-lang/types````` I assume the plan is still to disallow this? It has been a future-compat lint for a long time, seems ripe to go for hard error. However, turns out that outright removing it right now would lead to [tons of crater regressions](https://github.com/rust-lang/rust/pull/127655#issuecomment-2228285460), so for now this PR just makes this future-compat lint show up in cargo's reports, so people are warned when they use a dependency that is affected by this. Fixes https://github.com/rust-lang/rust/issues/27336 by removing the feature gate (so there's no way to silence the lint even on nightly) CC https://github.com/rust-lang/rust/issues/36887
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions