Skip to content

When a token has both a lexer warning and a lexer error, report the error #1321

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

Merged
merged 1 commit into from
Feb 9, 2023

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Feb 7, 2023

Otherwise, we would be suppressing lexer errors by warnings, accepting source code that should be invalid.

…rror

Otherwise, we would be surpressing lexer errors by warnings, accepting source code that should be invalid.
@ahoppen ahoppen force-pushed the ahoppen/prefer-error-over-warning branch from dbd0bd3 to d37fe3b Compare February 8, 2023 18:57
@ahoppen ahoppen changed the title When a token has both a lexer warning and a lexer error, report the error 🚥 #1320 When a token has both a lexer warning and a lexer error, report the error Feb 8, 2023
@ahoppen
Copy link
Member Author

ahoppen commented Feb 8, 2023

@swift-ci Please test

@ahoppen ahoppen requested a review from bnbarham February 8, 2023 18:58
@ahoppen
Copy link
Member Author

ahoppen commented Feb 8, 2023

@swift-ci Please test macOS

@kimdv
Copy link
Contributor

kimdv commented Feb 9, 2023

@swift-ci Please test macOS

@ahoppen ahoppen merged commit aff5499 into swiftlang:main Feb 9, 2023
@ahoppen ahoppen deleted the ahoppen/prefer-error-over-warning branch February 9, 2023 10:11
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.

3 participants