about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/src
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-06-13 14:05:19 +0000
committerbors <bors@rust-lang.org>2024-06-13 14:05:19 +0000
commitb6e5e3ffbbc41a7ef1f2a522fc7ded19b99918dc (patch)
tree21cb2758699310f1f86aef3317a3df84afd7a787 /compiler/rustc_codegen_gcc/src
parent9fdbfe1441a82e96e3f99ae199ff5348d8d948ae (diff)
parentea98e42bfd7e3723a68cb2dd6f6ac4a4866a400e (diff)
downloadrust-b6e5e3ffbbc41a7ef1f2a522fc7ded19b99918dc.tar.gz
rust-b6e5e3ffbbc41a7ef1f2a522fc7ded19b99918dc.zip
Auto merge of #125289 - WaffleLapkin:never-obligations, r=compiler-errors
Implement lint for obligations broken by never type fallback change

This is the second (and probably last major?) lint required for the never type fallback change.

The idea is to check if the code errors with `fallback = ()` and if it errors with `fallback = !` and if it went from "ok" to "error", lint.

I'm not happy with the diagnostic, ideally we'd highlight what bound is the problem. But I'm really unsure how to do that  (cc `@jackh726,` iirc you had some ideas?)

r? `@compiler-errors`

Thanks `@BoxyUwU` with helping with trait solver stuff when I was implementing the initial version of this lint.

Tracking:
- https://github.com/rust-lang/rust/issues/123748
Diffstat (limited to 'compiler/rustc_codegen_gcc/src')
0 files changed, 0 insertions, 0 deletions