Idea: Coalesce cache scans for batched source removal
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
No source files, tests, or entry points are named. Begin by collecting a real branch-switch or folder-removal trace, then measure time to fresh diagnostics as requested; the work is justified only if it shows a noticeable stall and preserves mixed-event ordering.
由索引模型根据 Issue 内容生成。
描述
Deferred idea
Removing a source file currently scans module ownership and the derived-query caches to discard affected entries. When one batch removes many warmed sources, those scans run again for every file. Consecutive removal-only events could be coalesced and retired together, so each cache is scanned only once. Any other event would first flush the pending removals, which keeps mixed-event ordering intact.
This is an idea to evaluate later, not a request to land the existing prototype.
Evidence so far
The benchmarks used real sources from the combined core+acme dependency closure: 631 packages and 7,371 sources, with modules checked before removal. The deletion scenarios themselves were constructed. They show the algorithmic cost but don't show a common workflow. For example, removing 100 sources cut the LSP watched-file handler median from 287 ms to 38 ms. Removing a single source doesn't benefit.
Why defer
- Deletions in a repository are usually sparse. Restarting the language server is a reasonable workaround for an occasional large batch.
- Branch switching might benefit, but it hasn't been measured. It also produces a mix of events rather than long runs of removals.
Revisit this after a real branch-switch or folder-removal trace shows a noticeable stall. At that point, measure the time to fresh diagnostics rather than claiming full-editor or cold-build gains.
Detailed measurements and prototype patches are in the investigation thread (Amp access required).
- 主要语言
- Rust
- 星标
- 125
- 派生
- 12
- 平均合并
- 7 小时 34 分钟
- 30 天内合并 PR
- 89
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
purefunctor/purescript-iris 的其他 Issue
-
diagnostics enhancement language-server
难度 3/5 1-2 天 新手友好度 72/100
purefunctor/purescript-iris#648 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
purefunctor/purescript-iris#613 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
purefunctor/purescript-iris#560 ·
维护者通常 1 天内回复
-
tooling
难度 4/5 3-5 天 新手友好度 58/100
purefunctor/purescript-iris#507 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
purefunctor/purescript-iris#264 ·
维护者通常 1 天内回复
查看 purefunctor/purescript-iris 的全部 Issue
相似的 Issue
-
needs triage
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 72/100
mozilla-services/syncstorage-rs#2715 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
-
documentation
难度 1/5 1 小时以内 新手友好度 82/100
physicsdolphin/nv-uefi-unlocker#53 · 4 个 reaction ·
维护者通常 1 天内回复