Performance History
Latest Results
docs(linter): document why some() is left alone for NaN and side effects
Two `Valid` examples covering the cases the rule deliberately does not
report, so the restriction reads as a decision rather than a gap:
a `NaN` search, which `includes()` would match under SameValueZero where
`x === NaN` never does, and a search value with side effects, which
`some()` evaluates once per element while `includes()` evaluates once.
acebot712:feat/use-includes-lastindexof-some
1 hour ago
perf(markdown): use lookup table
perf/markdown-parser
2 hours ago
perf(markdown): use lookup table
perf/markdown-parser
2 hours ago
perf(markdown): use lookup table
perf/markdown-parser
2 hours ago
perf(markdown): use lookup table
perf/markdown-parser
2 hours ago
perf(analyzer): faster conditional type inference
aminya:perf-inference
3 hours ago
[autofix.ci] apply automated fixes
dyc3/useFlatMathMinMax
8 hours ago
feat(lint/js): add `useFlatMathMinMax`
dyc3/useFlatMathMinMax
8 hours ago
Latest Branches
0%
23 hours ago
c9e746f
acebot712:feat/use-includes-lastindexof-some
+23%
2 hours ago
f27c547
perf/markdown-parser
-8%
23 hours ago
4717606
aminya:perf-inference