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

Should there be a more flexible parser for eol? #220

Open
github-actions bot opened this issue Jun 16, 2024 · 0 comments
Open

Should there be a more flexible parser for eol? #220

github-actions bot opened this issue Jun 16, 2024 · 0 comments

Comments

@github-actions
Copy link

Line: 517

}
fn parse_comment_(i: &str) -> AsmResult<Token> {
// TODO: Should there be a more flexible parser for eol?
// category=Toolchain
// TODO: Comments with nothing after the semicolon currently fail
// category=Toolchain
map(pair(char(';'), cut(is_not("\n\r"))), |_| Token::Comment)(i)
}
fn parse_comment(i: &str) -> AsmResult<Token> {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants