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

Can't parse 128-bit integer literals #114

Closed
Arnavion opened this issue Apr 21, 2017 · 1 comment · Fixed by #156
Closed

Can't parse 128-bit integer literals #114

Arnavion opened this issue Apr 21, 2017 · 1 comment · Fixed by #156
Labels

Comments

@Arnavion
Copy link
Contributor

Arnavion commented Apr 21, 2017

As part of updating the tests/rust submodule for the catch-expressions PR, I found syn can't parse u128 literals.

let raw = "0x112233445566778899aabbccddeeff11u128";
let actual = parse_expr(raw).unwrap(); // fails

Prevents test_round_trip from parsing atleast tests/rust/src/libstd/net/ip.rs (parse_crate stops before the entire mod tests item that contains the literal, then complains that there are unparsed tokens).

Affected files:

@dtolnay dtolnay added the syntax label Apr 21, 2017
@dtolnay
Copy link
Owner

dtolnay commented Apr 21, 2017

Thanks! We will need to figure out how to represent the parsed result. Libsyntax just puts i128/u128 in the AST but we can't do that on stable.

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

Successfully merging a pull request may close this issue.

2 participants