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.

Sign up for GitHub

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

Jump to bottom

i16 literals have a blatantly wrong range #2462

Closed
msullivan opened this issue May 29, 2012 · 1 comment
Closed

i16 literals have a blatantly wrong range #2462

msullivan opened this issue May 29, 2012 · 1 comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@msullivan
Copy link
Contributor

The maximum value of an i16 literal is 2048, which is just clearly wrong.
@msullivan msullivan mentioned this issue May 29, 2012
Closed
@msullivan
Copy link
Contributor Author

This is split off of Issue #2438.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msullivan