Skip to content

[Diagnostics][NFC]Move fix-it text formatting later in the diagnostics pipeline #26711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

owenv
Copy link
Contributor

@owenv owenv commented Aug 18, 2019

This builds on and includes the commit from #26612

Defer fix-it text formatting to individual DiagnosticConsumers so it can be customized or omitted as needed, similar to how it's done for errors, warnings, and notes

Move DiagnosticArgument, DiagnosticFormatOptions, and formatDiagnosticText out of DiagnosticEngine and into DiagnosticFormatting, to avoid circular dependencies between DiagnosticEngine and DiagnosticConsumer (this is the bulk of the diff, but should be a generally beneficial refactor)

owenv added 2 commits August 14, 2019 20:22
These are defined with macros like errors/warnings/notes, and
make use of format strings and diagnostic arguments. The intent
is to leverage diagnostic arguments in the future to disambiguate
ambiguously spelled types.

Ported a few miscellaneous fix-its to the new system
Defer fix-it text formatting to individual DiagnosticConsumers so
it can be customized or omitted as needed, similar to how it's done
for errors, warnings, and notes

Move DiagnosticArgument, DiagnosticFormatOptions, and
formatDiagnosticText out of DiagnosticEngine and into
DiagnosticFormatting, to avoid circular dependencies between
DiagnosticEngine and DiagnosticConsumer
@owenv owenv closed this Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant