diff options
| author | bors <bors@rust-lang.org> | 2025-08-10 17:44:40 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-08-10 17:44:40 +0000 |
| commit | 29737cb44beb67dbcf001ca1f11b7ec8964d8d06 (patch) | |
| tree | 93298f90fab4215b84309cbd82aa1b958d8d8194 /compiler/rustc_pattern_analysis | |
| parent | 18eeac04fc5c2a4c4a8020dbdf1c652077ad0e4e (diff) | |
| parent | b2b4bd41fa844bed05a21872162f5a6a333f2bcc (diff) | |
| download | rust-29737cb44beb67dbcf001ca1f11b7ec8964d8d06.tar.gz rust-29737cb44beb67dbcf001ca1f11b7ec8964d8d06.zip | |
Auto merge of #144544 - JonathanBrouwer:illformed-in-deps, r=traviscross
Start reporting future breakage for `ILL_FORMED_ATTRIBUTE_INPUT` in dependencies This has been a warn lint since early 2019 and a deny-by-default lint since late 2019. We're currently transitioning some of the cases where this lint is being produced to a hard error (https://github.com/rust-lang/rust/pull/143607 https://github.com/rust-lang/rust/pull/143808 and more) So let's report this lint in all dependencies for the remaining attributes r? `@traviscross` `@rustbot` labels +I-lang-nominated +T-lang -T-compiler cc `@jdonszelmann` (Separate question: Why does the "Future incompatibility report" only trigger if `report_in_deps` is true, even if the future incompatibility happens in the same crate, is this correct?) This also needs a crater run, but I don't have permissions to trigger this
Diffstat (limited to 'compiler/rustc_pattern_analysis')
0 files changed, 0 insertions, 0 deletions