Skip to content

Can we make parsers stateless? #42

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

Open
rcshubhadeep opened this issue Nov 4, 2020 · 0 comments
Open

Can we make parsers stateless? #42

rcshubhadeep opened this issue Nov 4, 2020 · 0 comments
Labels
discussion question Further information is requested

Comments

@rcshubhadeep
Copy link
Contributor

Right now Parser objects are stateful (in a sense that each obejct keep the parse tree internally and also the raw code and all, of the file / code string that it parsed last)

Questions

  • Is it necessary to make them stateless (imagine creating a single parser and using it in parallel on multiple files using a thread or multi-process based architecture)

  • If the answer to the above is Yes then how do we do that?


This may need a significant re-design of tree-hugger works at the moment. So, if we do that we need to keep in mind that we must not break backward compatibility.

@rcshubhadeep rcshubhadeep added discussion question Further information is requested labels Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant