Test for GC in fromPointToPoint
Open
Nobody has claimed this yet.
type/perf
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently we implement fromPointToPoint as fromDirection by creating dir vector on the fly and saving on the 95% same code. But is it at cost of GC garbage?
Contributor guide
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 the fromPointToPoint and fromDirection entry points in the repository and inspect how the direction vector is created. Add or identify a focused test or benchmark that can determine whether this implementation creates GC garbage. Done means the cost is measured and the result is captured clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100