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

Consider splitting LiteralNumericExpression to LiteralInt32Expression + LiteralFloatExpression #73

Open
dead-claudia opened this issue Feb 20, 2019 · 0 comments
Open

Consider splitting LiteralNumericExpression to LiteralInt32Expression + LiteralFloatExpression #73

dead-claudia opened this issue Feb 20, 2019 · 0 comments

Comments

@dead-claudia
Copy link

Engines heavily optimize integers, and they do currently parse 1 and 1.0 differently, taking 1.0 as a hint it's likely used as a floating point number and 1 as a hint it's likely used as a simple integer. Shouldn't the AST reflect this reality by giving them this helpful little tip?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dead-claudia