Fix failure to parse rustc's JSON output if it is too nested #11368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR try to resolve?
The structure of rustc's JSON outputs is recursive. See https://docs.rs/rustfix/0.6.1/rustfix/diagnostics/struct.Diagnostic.html which has a field
children: Vec<Self>
. When macros are involved, this output can end up getting arbitrarily deeply nested, and eventually causes Cargo to fail to parse it. In this situation Cargo will just dump the entire unformatted JSON output through to stderr instead of a rendered diagnostic.This PR makes Cargo able to safely pick out a rendered diagnostic from arbitrarily deeply nested rustc JSONs.
How should we test and review this PR?
Before: 335 Kilobytes of unformatted JSON
After: rendered diagnostic as expected.