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

Mutalyzer normalize is very slow due to repeated initialization of lark parser #34

Open
yfarjoun opened this issue Nov 12, 2024 · 0 comments
Open

Mutalyzer normalize is very slow due to repeated initialization of lark parser #34

yfarjoun opened this issue Nov 12, 2024 · 0 comments

Comments

@yfarjoun
Copy link
Contributor

In the current implementation normalize initialized a new parser for every normalize call. this end up costing much more than the parse call.

Since normalize uses 1 of two possible parsers (it seems) one could simply use a cache to obtain the right parser.

fixed in #33
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
@yfarjoun