# I wish Zig team did something like this

**URL:** <https://ziggit.dev/t/i-wish-zig-team-did-something-like-this/18304>\
**Category:** Brainstorming\
**Created:** [November 10, 2026, 8:21pm UTC](https://ziggit.dev/t/i-wish-zig-team-did-something-like-this/18304 "2026-11-10T20:21:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cztomsik](https://ziggit.dev/user_avatar/ziggit.dev/cztomsik/32/3032_2.png) [@cztomsik](https://ziggit.dev/u/cztomsik)\
**Post date:** [November 10, 2026, 8:21pm UTC](https://ziggit.dev/t/i-wish-zig-team-did-something-like-this/18304/1 "2026-11-10T20:21:13Z")

</div>

Not just the general theme of speeding up the compiler

> **[How to speed up the Rust compiler in November 2026](https://nnethercote.github.io/2026/11/04/how-to-speed-up-the-rust-compiler-in-november-2026.html)**
>
> My first month working on Rust compiler performance for Hexcat is over and it’s time to see some of what’s happened since my last post.

But if you click through those PRs, you can see a batch run of the most common repos, and how much compilation time improved on each

EDIT: it would be also easier to estimate blast radius of any upcoming/drafted Zig lang breaking change

---

<div class="post-metadata">

**Author:** ![gwenzek](https://ziggit.dev/user_avatar/ziggit.dev/gwenzek/32/8137_2.png) [@gwenzek](https://ziggit.dev/u/gwenzek)\
**Post date:** [November 10, 2026, 8:40pm UTC](https://ziggit.dev/t/i-wish-zig-team-did-something-like-this/18304/2 "2026-11-10T20:40:05Z")

</div>

There was [Performance Tracking ⚡ Zig Programming Language](https://ziglang.org/perf/) but it’s dead for some time now.  
IIUC contributions here would be welcome