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

Abstract Syntax Tree #57

Open
Zomis opened this issue Nov 1, 2016 · 1 comment
Open

Abstract Syntax Tree #57

Zomis opened this issue Nov 1, 2016 · 1 comment

Comments

@Zomis
Copy link
Owner

Zomis commented Nov 1, 2016

If @retailcoder can do it then so can I. And in fact, it would be useful to have it.

At the moment I need to run the code in order to analyze it, with an AST, the code could be analyzed and simplified, and hints/warnings/errors shown without the code being executed.

This could also have major impact on the core code, as data structures can be changed and code could run faster.

An important question is: Should each token know its span to be shown in the IDE?

@Zomis
Copy link
Owner Author

Zomis commented Nov 7, 2016

We'll start with each token knowing its span, I believe that it should not cause any problems.

The goal with the AST is to implement static code analysis and to possibly improve the runspeed of code (although compile time will increase)

As a start, the code will only be lexed and parsed at specific occasions, a future goal would be to lex and parse the code as the IDE is edited, see http://chat.stackexchange.com/transcript/8595?m=33308498#33308498

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