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

Tracking issue for RFC 463 - tokenise idents immediately after a literal as part of the literal #19088

Closed
nrc opened this issue Nov 18, 2014 · 1 comment · Fixed by #19103
Closed
Assignees
Labels
A-parser Area: The parsing of Rust source code to an AST B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@nrc
Copy link
Member

nrc commented Nov 18, 2014

This is backwards incompatible, but we do not want to block 1.0.

@nrc nrc added E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. A-parser Area: The parsing of Rust source code to an AST I-nominated B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. labels Nov 18, 2014
@nrc
Copy link
Member Author

nrc commented Nov 18, 2014

RFC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-parser Area: The parsing of Rust source code to an AST B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants