Add future-incompat entries to json diagnostic output #315
Labels
major-change
A proposal to make a major change to rustc
major-change-accepted
A major change proposal that was accepted
T-compiler
Add this label so rfcbot knows to poll the compiler team
Proposal
Add future-incompat entries to json diagnostic output. (Also, ensure we always run code for future-incompatibility lints, even if they are allowed.)
This is part of rust-lang/rust#71249 (rust-lang/rfcs#2834); it is the implementation of the
rustc
side of that feature.This change is broken into these main parts:
compiletest
to be able to handle the generated JSON output.compiletest
will convert these generated JSON entries to stderr diagnostics (as opposed to just discarding them, as it currently does for artifact notifications), even though a normal user running in human-readable diagnostic mode will not observe them.Mentors or Reviewers
I have a prototype implementation: https://github.com/pnkfelix/rust/tree/prototype-rustc-side-of-report-future-incompat
I plan to mentor the work (or finish the above prototype).
Process
The main points of the Major Change Process is as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: