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

Use Shunting-Yard #22

Open
napen123 opened this issue Jun 2, 2019 · 0 comments
Open

Use Shunting-Yard #22

napen123 opened this issue Jun 2, 2019 · 0 comments
Assignees

Comments

@napen123
Copy link
Member

napen123 commented Jun 2, 2019

I believe rewriting the parser to use the shunting-yard algorithm is something we should look into.

The current way we parse input can do so reasonably well, but it's lacking in several areas (see #21, #17, #2, and possibly #4). Because of this, I think beefing up the parser and using something like shunting-yard would make things easier to follow and would provide us with many improvements pretty much immediately (e.g. unary operators).

I'd imagine this would warrant a major release and may result in a slight performance hit, but I think it's worth it.

@napen123 napen123 self-assigned this Jun 2, 2019
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

1 participant