Closed kaleidawave closed 2 months ago
Now not cloning sources and reusing the &str
source when printing diagnostics. But hasn't really touched the dial.
Summary
Warning: Ignoring non-zero exit code.
./target/release/ezno check demo.ts --count-diagnostics ran
1.05 ± 0.07 times faster than ./target/release/ezno check demo.ts --compact-diagnostics
2.40 ± 0.12 times faster than ./target/release/ezno check demo.ts
Moving on
--count-diagnostics
or --compact-diagnostics
in those casescodespan_reporting
library or just the fact that printing a lot of lines to the console is expensiveOn the ongoing quest to figure why the diagnostics emit takes 60% of ezno check
time on the total specification
Going to try on this branch later, maybe trying more complex diagnostics will show a change?
ezno check
to print warnings (fixed where it only printed diagnostics if there was errors)RangeMap
methodsutils
toutilities
(in checker)Couldn't get the to the bottom of diagnostic emit overhead. Leaving for later