Terminal engine: single pass over PTY bytes before the parser

未关闭
#252 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
performance

调研方向

Start by reading crates/atlas-term/src/vt/mod.rs where Vt::feed calls ClearScan::scan, PixelScan::scan and the shell scanner before Processor::advance; then read vt/scan.rs and vt/pixel.rs to see the per-byte loops. Run the existing split-safe tests first to establish a green baseline, then use the #239 harness on the ASCII, unicode and agent TUI corpora to record parse-only MB/s before changing anything. Done means those numbers improve with no behaviour change and the split-safe tests still passing.

由索引模型根据 Issue 内容生成。

描述

area: terminal priority: 2 normal status: confirmed type: feature

Research: discussion #237 (Linux/engine comment). Applies to macOS, Windows and Linux (shared atlas-term). Measure with the #239 harness before and after.

Problem (read in code)

Vt::feed (crates/atlas-term/src/vt/mod.rs) scans every chunk with ClearScan::scan (vt/scan.rs, a per-byte loop) and feed_part with PixelScan::scan (vt/pixel.rs, per-byte match) and the shell scanner before Processor::advance. Only the shell scanner (SeqScan) jumps to the next ESC.

Change

Enter these state machines only at ESC (memchr), or merge them into one pass. The split-safe tests already exist and must stay green.

Why

Ghostty found 9–25% of parse time in short-run setup and scanning (ghostty-org/ghostty#13226) [their measurement].

Done when

Parse-only MB/s up on the #239 corpora (ASCII, unicode, agent TUI capture), no behaviour change.

主要语言
Rust
星标
3
派生
1
平均合并
9 小时 51 分钟
30 天内合并 PR
310

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。