Use ju.Function instead of js.Function1 in RedBlackTree.fromOrdered #5224
Conversation
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
Replace `js.Function1` with `java.util.Function` in `java.util.RedBlackTree.fromOrdered` to eliminate JS interop overhead when constructing the tree from sorted collections (used for TreeMap and TreeSet). According to the micro benchmark: this change provides performance improvements on WebAssembly while maintaining identical performance on JavaScript runtime: tanishiking/scalajs-benchmarks#5 - 4-5x faster TreeMap/TreeSet construction from SortedMap/Set on Wasm - No performance regression on JS
sjrd
approved these changes
Aug 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replace
js.Function1withjava.util.Functioninjava.util.RedBlackTree.fromOrderedto eliminate JS interop overhead when constructing the tree from sorted collections (used for TreeMap and TreeSet). According to the micro benchmark: this change provides performance improvements on WebAssembly while maintaining identical performance on JavaScript runtime: tanishiking/scalajs-benchmarks#5