LivelyKernel / LivelyKernel/lively.morphic
[changes] only record change if value really changes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This should make it easier to maintain the change recording and make use of it for other purposes.
We need to make sure that the equality tests don't get to expensive, though.
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
The issue does not name any files, tests, or entry points. Locate the change-recording implementation, then determine how equality should prevent recording unchanged values without making comparisons too expensive. Done means unchanged values are not recorded and the performance concern is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100