sv-parser
sv-parser copied to clipboard
Compilation Speed
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:
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.
@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.