We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This fails parsing
mod foo #breaking comment
I dont see anything that should be problematic with this approach? Specifically I can see that modules are only matched when:
Some(Keyword::Mod) if self.next_are(&[Identifier, Identifier, StringToken]) || self.next_are(&[Identifier, Identifier, Identifier, StringToken]) || self.next_are(&[Identifier, Identifier, Eof]) || self.next_are(&[Identifier, Identifier, Eol]) || self.next_are(&[Identifier, QuestionMark]) =>
Is there a reason to explicitly match on Eof and Eol? Also what does the triple indentifier, StringToken match?
Eof
Eol
The text was updated successfully, but these errors were encountered:
mod
Good catch! Fixed in #2201.
Identifier, Identifier, Identifier, StringToken catches this case, which uses a shell-expanded string:
Identifier, Identifier, Identifier, StringToken
mod foo x"$HELLO/bar.just"
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
This fails parsing
I dont see anything that should be problematic with this approach?
Specifically I can see that modules are only matched when:
Is there a reason to explicitly match on
Eof
andEol
?Also what does the triple indentifier, StringToken match?
The text was updated successfully, but these errors were encountered: