Terminal engine spike: libghostty-vt as the VT core behind vt/

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
22/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, rust
领域
performance

调研方向

Start with discussion #237 and the #239 benchmark harness, since every number in the write-up has to come from it; the engine boundary is vt/mod.rs, and the call sites that would break on a swap are frame.rs, pick.rs, find.rs, the selection code and images.rs because they use alacritty Term/Grid APIs. Run the corpora through both engines in parse-only and snapshot modes, recording MB/s and RSS, and add the many-unique-styles full-redraw corpus the caveat calls out. Done means numbers plus a gap list (OSC 133/7/9/777, sixel, DECSET 1016, sync hold, render-state copy cost, Zig-in-CI cost) posted to #237 with an adopt/defer/drop call.

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

描述

area: terminal priority: 3 low 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.

Context

libghostty-vt 1.0 (2026-11): MIT, stable C ABI, no threads, SIMD parser (Ghostty reports 342 MB/s on a real 2.6 GB corpus, 725 MB/s synthetic ASCII), compressed scrollback, full kitty graphics; used by JetBrains and Neovim. Rust crate libghostty-vt 0.2 (pre-1.0) needs Zig 0.17 at build time. vt/mod.rs was isolated for this swap, but frame.rs, pick.rs, find.rs, selection and images.rs use alacritty Term/Grid APIs.

Spike (time-boxed, no commitment)

Feed the #239 corpora through both engines (parse-only and with snapshot), compare MB/s and RSS; list gaps: OSC 133/7/9/777, sixel, DECSET 1016, sync hold, render-state copy cost; cost of Zig in CI on all three OSes.

Caveat

Ghostty's maintainer says full-screen redraws with many unique styles are a known slow path, the pattern agent TUIs produce. Measure that corpus specifically.

Done when

A write-up in #237 with numbers: adopt, defer or drop.

主要语言
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 摘要。