RoaringBitmap / RoaringBitmap/roaring
ParHeapOr, ParAnd: avoid allocations while using sync.Pool
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
staticcheck reports
parallel.go:224:12: argument should be pointer-like to avoid allocations (SA6002)
parallel.go:243:12: argument should be pointer-like to avoid allocations (SA6002)
docs for this issue can be found here: https://github.com/dominikh/go-tools/blob/master/cmd/staticcheck/docs/checks/SA6002
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
Start in parallel.go at lines 224 and 243, where staticcheck reports SA6002 for sync.Pool usage. Run staticcheck on the package and inspect ParHeapOr and ParAnd; done means the reported allocation warnings are resolved while the existing parallel operations retain their behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100