Mutability as a first-class concept — Make cachew aware of which objects are mutable vs immutable, so it can automatically maintain the invalidation map whenever a mutable object changes.
Open
- Dominant language
- Go
- Stars
- 41
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
The issue body names no files, tests, or entry points. Start by surveying cachew's cache and invalidation-map implementation, then determine how mutability is represented and observed. Done means cachew distinguishes mutable from immutable objects and automatically keeps the invalidation map current when mutable objects change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100