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

Compilation Speed #32

Open
SeanMcLoughlin opened this issue Apr 29, 2021 · 1 comment
Open

Compilation Speed #32

SeanMcLoughlin opened this issue Apr 29, 2021 · 1 comment

Comments

@SeanMcLoughlin
Copy link
Contributor

Compilation of this crate is extremely slow to the point of not being able to use an on-the-fly linter at all, making working with this crate difficult.

I've run some profiling using this unstable feature. Below is a screenshot of the report:
Screenshot_20210428_210925

Running self-profiling shows that the longest sections of compilation time have to do with proc_macro expansion. For sv-parser-parser, this is definitely due to the macros for packrat parsing/tracing. For sv-parser-syntaxtree, it's due to all of the derive macros.

I know this is a difficult problem to solve, but I'm curious if there's been any thought on how to improve the compilation speeds of these crates.

@DaveMcEwan
Copy link

@SeanMcLoughlin Is this still a problem? Can you describe your usecase?
You don't need to recompile sv-parser every time you want to run svlint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants