diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-03 11:33:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-03 11:33:36 +0200 |
| commit | 71009058b0af9dea42e67c83f8198b6c1dde79ce (patch) | |
| tree | f3205af285a78a5d7e402764ca89b9f93f9b1205 /compiler/rustc_codegen_gcc/src | |
| parent | 94da3d9c700df20446623c800919819d7581f9c1 (diff) | |
| parent | 9b7da4deb2868eae4a8c4154045ae3e67ee74de7 (diff) | |
| download | rust-71009058b0af9dea42e67c83f8198b6c1dde79ce.tar.gz rust-71009058b0af9dea42e67c83f8198b6c1dde79ce.zip | |
Rollup merge of #141936 - WaffleLapkin:report-in-deps-decoupling, r=oli-obk
Decouple "reporting in deps" from `FutureIncompatibilityReason` The reason should just be it -- the reason. It never felt right to me that it was also responsible for whatever we include the warning in cargo's reports. It gets especially unruly if you want to add non-`FutureReleaseError*` warnings which are included in the reports. I just added a field to `FutureIncompatibleInfo` to control whatever the diagnostic is included in the cargo's reports.
Diffstat (limited to 'compiler/rustc_codegen_gcc/src')
0 files changed, 0 insertions, 0 deletions