docs+feat: sync roadmap to v5.10.4 and add benchmark suite - #100
Open
mcabreradev wants to merge 2 commits into
Open
mcabreradev wants to merge 2 commits into
mcabreradev wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Reconcilia el roadmap del proyecto con la realidad del repo (estaba congelado en v5.6.0 cuando el repo ya va por v5.10.4) y añade la suite de benchmarks que el roadmap tenía pendiente.
Changes
docs: sync roadmap to repo reality (v5.10.4)
orderBy), integraciones Angular/SolidJS/Preact, performance monitorfeat: add benchmark suite (vitest bench)
benchmarks/con Vitest benchmark API:pnpm benchmarkfilter.bench.ts(expresiones comunes, 100→100K items),cache.bench.ts(cold vs warm, escalado),operators.bench.ts(operador vs predicado, eager vs lazy, early exit),wildcards.bench.ts(patrones con/sin caché)helpers.tsdeterminista (misma seed cada run) para runs comparablesREADME.mdde benchmarks: cómo correr, cómo interpretar, por qué no van en CIbenchmarkenpackage.jsonVerified
benchmarkcorre y entrega datos reales. Dos claims del roadmap validados:Note
Los benchmarks quedan fuera de CI a propósito (timing-based, flaky en runners compartidos). Si se quiere un workflow separado o umbrales de regresión, es una decisión aparte.