You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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. Forsv-parser-parser
, this is definitely due to the macros for packrat parsing/tracing. Forsv-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.
The text was updated successfully, but these errors were encountered: