DonIsaac 270fc53401 chore(bench): include fixers in linter benchmarks (#5307) ... Fixing code is an important part of linter logic. We want to make sure fixers for each rule, and the code responsible for applying those fixes, are included in benchmarks. As it currently stands, fixer closures are applied regardless of whether the user wants fixers to be applied. However, this is an implementation detail and is subject to change. I also want to bench the performance of `Fixer`.		2024-08-28 23:19:43 +00:00
..
codegen.rs	chore(benchmark): add codegen benchmark (#4207)	2024-07-11 23:58:37 +08:00
isolated_declarations.rs	chore(benchmark): add isolated declarations (#4078)	2024-07-07 17:14:48 +08:00
lexer.rs
linter.rs	chore(bench): include fixers in linter benchmarks (#5307)	2024-08-28 23:19:43 +00:00
minifier.rs	perf(minifier): only visit arrow expression after dropping console.log (#4677)	2024-08-06 04:20:41 +00:00
parser.rs	chore(tasks): parse regular expression in parser benchmark (#5212)	2024-08-26 13:11:09 +08:00
parser_napi.rs	chore: improve some format by running cargo +nightly fmt	2024-06-19 00:48:30 +08:00
prettier.rs
semantic.rs	refactor(ci): include drop in semantic benchmark (#5245)	2024-08-27 09:30:52 +08:00
sourcemap.rs	feat(sourcemap): add ConcatSourceMapBuilder::from_sourcemaps (#4639)	2024-08-06 14:08:17 +08:00
transformer.rs	ci: transformer benchmark measure transformer itself only (#5193)	2024-08-27 01:53:27 +00:00