diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-05-20 08:31:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-20 08:31:41 +0200 |
| commit | 88552615e87028fe591486ba0bc166623711047e (patch) | |
| tree | cd39e79609433bb266d17e3ee9176f1183e2e29a /compiler/rustc_codegen_llvm/src | |
| parent | 738941628457d315cf91c77e4aeeb54b9c35bd50 (diff) | |
| parent | 434221ba45ffb03e8e837c62543eee7c5b3c62f1 (diff) | |
| download | rust-88552615e87028fe591486ba0bc166623711047e.tar.gz rust-88552615e87028fe591486ba0bc166623711047e.zip | |
Rollup merge of #125282 - WaffleLapkin:never-type-unsafe-improvements, r=compiler-errors
Never type unsafe lint improvements
- Move linting code to a separate method
- Remove mentions of `core::convert::absurd` (#124311 was rejected)
- Make the lint into FCW
The last thing is a bit weird though. On one hand it should be `EditionSemanticsChange(2024)`, but on the other hand it shouldn't, because we also plan to break it on all editions some time later. _Also_, it's weird that we don't have `FutureReleaseSemanticsChangeReportInDeps`, IMO "this might cause UB in a future release" is important enough to be reported in deps...
IMO we ought to have three enums instead of [`FutureIncompatibilityReason`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint_defs/enum.FutureIncompatibilityReason.html#):
```rust
enum IncompatibilityWhen {
FutureRelease,
Edition(Edition),
}
enum IncompatibilyWhat {
Error,
SemanticChange,
}
enum IncompatibilityReportInDeps {
No,
Yes,
}
```
Tracking:
- https://github.com/rust-lang/rust/issues/123748
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
