Investigate and document performance
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- JavaScript
- Stars
- 507
- Forks
- 45
- Avg merge
- 11h 22m
- Merged PRs (30d)
- 4
Description
Here is example of slow and fast code for calculating factorial of 1000:
;; slow
(--> (new Array 1000) (fill 0) (map (curry (n-ary 3 +) 1)) (reduce (binary *)))
;; same but faster
(--> (new Array 1000) (fill 0) (map (lambda (_ i) (+ i 1))) (reduce (lambda (a b) (* a b))))
;; faster and simpler
(apply * (cdr (range 1001)))
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
Start by comparing the three Scheme factorial examples in the issue and measure their relative performance in the LIPS interpreter. Investigate why the slower forms differ from the simpler form, then document the findings and the completed performance guidance in the relevant project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100