Investigate optimizing `HistoryTracker.addChange()`
Open
@J-Fields is already working on this.
Since Jan 9, 2020.
area/performance
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
I stumbled across a comment @johnfn made in this function which I think deserves some testing and some thought; this ticket exists to remind me to do both. On large files, I suspect this is very inefficient and may contribute to the slowdown we experience. First step is to do some profiling.
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.
Assessment
This issue has not been assessed yet.