Skip to content
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

Fix error when lexing language list. #4784

Merged
merged 1 commit into from
Mar 10, 2020
Merged

Conversation

martinmr
Copy link
Contributor

@martinmr martinmr commented Feb 15, 2020

A language list with the value "*:." is lexed correctly and an error
saying that if all the languages (the meaning of the character *) are
requested, the language list should only have one element.

But a language list with the value ".:*" fails with a lexing error. This
change changes the lexer so that the two lists fail with the same error.


This change is Reviewable

A language list with the value "*:." is lexed correctly and an error
saying that if all the languages (the meaning of the character *) are
requested, the language list should only have one element.

But a language list with the value ".:*" fails with a lexing error. This
change changes the lexer so that the two lists fail with the same error.
@martinmr martinmr requested review from manishrjain and a team as code owners February 15, 2020 00:15
@martinmr martinmr merged commit 07481d6 into master Mar 10, 2020
@martinmr martinmr deleted the martinmr/lang-lex-error branch March 10, 2020 17:56
martinmr added a commit that referenced this pull request Mar 17, 2020
A language list with the value "*:." is lexed correctly and an error
saying that if all the languages (the meaning of the character *) are
requested, the language list should only have one element.

But a language list with the value ".:*" fails with a lexing error. This
change changes the lexer so that the two lists fail with the same error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant