How AST-grep Rewrote Tree-sitter in Rust and Made It 30% Faster
herrington_d
85 points
15 comments
July 26, 2026
Related Discussions
Found 5 related stories in 60.6ms across 6,054 title embeddings via pgvector HNSW
- Scaling Memory Safety: AI-Assisted Rewrites of C/C++ Dependencies to Rust afdbcreid · 15 pts · August 24, 2026 · 54% similar
- Bun 1.4 Rust rewrite is not looking good? tipiirai · 136 pts · August 19, 2026 · 53% similar
- Rust Glancer: Rust LSP using 100x less RAM matklad · 103 pts · August 21, 2026 · 53% similar
- How is the Bun rewrite in Rust going? tomlockwood · 463 pts · July 27, 2026 · 53% similar
- How Our Rust-to-Zig Rewrite Is Going jorangreef · 467 pts · July 16, 2026 · 52% similar
Discussion Highlights (6 comments)
AlexeyBrin
Reading the article is like climbing a load-bearing wall to quote their last phrase.
trickypr
> incremental old-tree reuse were removed Maybe I am missing what they meant here, but isn’t the entire point of tree-sitter that you can reuse old trees to make edit updates faster? It is seems quite probable that all the performance gains came from optimising for fixed files with no error recovery, at the cost of how ts is actually used.
gumby
Even this AI generated article hs a hard on for rust. If all references to switching to rust were eliminated the article would be the same.
senderista
I’m always so disoriented by wondering how to interpret the pronoun “I” in these AI-generated articles.
nullbio
ast-grep is a great tool. Really helps with agentic work. I wish the LLMs were trained to use it by default. Would make them incredibly powerful.
why_only_15
I really don't like this. Don't post your AI-generated articles here. https://www.pangram.com/history/fce67fb4-4f6a-4eb4-a323-5048...