[DEV] Optimize MergeUtil#mergeCollections
Open
Nobody has claimed this yet.
Tech Debt
- Dominant language
- Java
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
minimize amount of lists to use ForkJoin instead of plain code on merging collections
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate MergeUtil#mergeCollections and read its current collection-merging path first. Determine where list allocations occur and how the existing plain implementation works before evaluating ForkJoin. Done means preserving merge behavior while reducing unnecessary lists and using ForkJoin where it improves the operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100