New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize traverse #4498
Optimize traverse #4498
Commits on Aug 18, 2023
Commits on Aug 21, 2023
Commits on Aug 22, 2023
-
-
-
-
-
Optimize {Seq, Queue, Vector, ArraySeq} traverseFilter for
StackSafeMonads
-
-
Commits on Aug 23, 2023
-
Optimize Vector traverse_ for StackSafeMonads
Also fix 2.12 errors
-
Add extra laws tests so we test the multiple branches corresponding to
different runtime types for the Applicative instance
-
Commits on Aug 25, 2023
Commits on Nov 8, 2023
-
Experiment: use immutable data structures in optimized traverse
Is this necessary? The monad laws should ensure that it's safe to use mutable builders. Nonetheless it will be good to confirm the performance delta for using immutable data structures
Commits on Nov 10, 2023
-
Experiment: use immutable List for optimized traverse
To see if this is more performant than an immutable vector
Commits on Nov 14, 2023
-
Use applicative methods instead of flatMap
For the benefit of Monads with optimized Applicative operations eg parsers
Commits on Dec 8, 2023
Commits on Dec 13, 2023
Commits on Dec 19, 2023
-
Vector-based optimized traverse and traverseFilter in the same commit
for the sake of benchmarking
Commits on Dec 22, 2023
Commits on Mar 4, 2024
-
Revert "Retroactive attempt to establish a baseline including the new…
… benchmarks" This reverts commit b08196e. We've got our baseline benchmarks now
-
Commits on Mar 5, 2024
Commits on Mar 7, 2024
Commits on Mar 22, 2024
Commits on Mar 26, 2024
-
Merge pull request #2 from valencik/more-chain
Use `Chain` in `traverseDirectly` helpers