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

Should we move our constant folding optimizations to a single place in the code? #77

Open
hugomg opened this issue Dec 4, 2017 · 0 comments
Open

Should we move our constant folding optimizations to a single place in the code? #77

hugomg opened this issue Dec 4, 2017 · 0 comments
Labels
enhancement

Comments

@hugomg
Copy link
Contributor

hugomg commented Dec 4, 2017

Currently, there is constant folding logic spread around the whole compiler. The parser does constand folding for .. operators and the code generator does some constant folding in the parameters of numeric for loops.

Perhaps these would belong together in a separate constant folding subroutine?
@hugomg hugomg changed the title Should we move our constant folding optimizations to a single place in the code Should we move our constant folding optimizations to a single place in the code? Dec 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hugomg