consider memoizing smarter
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 87
- Forks
- 28
- Avg merge
- 3h 27m
- Merged PRs (30d)
- 27
Description
Issues such as #131 suggest we may want to:
- have a fixed-sized cache for memoizing
- memoize methods by hanging the cache off of the object (instead of a global dict), to avoid dict lookups
- think more carefully about what we memoize and avoid memoizing things that are reasonably fast to compute
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 reviewing the concerns raised in issue #131 and the existing memoization behavior. Clarify the desired fixed cache size, per-object cache ownership, and which computations should be memoized. Done requires an agreed design and corresponding implementation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100