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
names I would pick: TokenType becomes Token TokenKind becomes TokenType Token becomes SpannedToken TokenReference becomes... SpannedTokenWithTrivia?
names I would pick:
Based on @tomprince's work, TokenReference will be WithTrivia<Token>, and potentially Token to Spanned<Token>.
WithTrivia<Token>
Token
Spanned<Token>
The text was updated successfully, but these errors were encountered:
I think TokenKind is a better name than TokenType. It lines up better with all the ErrorKind enums, which serve a similar purpose.
TokenKind
TokenType
ErrorKind
Sorry, something went wrong.
Yeah, I agree, I'm just copying the old message.
No branches or pull requests
Based on @tomprince's work, TokenReference will be
WithTrivia<Token>
, and potentiallyToken
toSpanned<Token>
.The text was updated successfully, but these errors were encountered: