luckyframework / luckyframework/lucky_cache
Max cache option
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
SplayTreeMap supports a maxsize option:
```
stm = SplayTreeMap(String, String).new
stm.maxsize = 10
```
I think this just limits the number of keys you can store... Part of me thinks a file size option may be better in some cases :thinking: Like, don't let my cache go over 10mb.... I'm not sure how we could do that reliably, or efficiently, but I wanted to at least jot it down.
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 with the SplayTreeMap entry point and its existing maxsize option. Clarify whether the goal is a key-count limit or a file-size limit, then define how cache size should be measured and what behavior would count as complete before adding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100