For the past year and a half, the team building Roc's compiler has been rewriting our 300,000 lines of Rust code into Zig, for reasons I'll recap below. We recently passed an exciting milestone: feature parity with the original compiler!
Announcing Rust 1.12.1 | Rust Blog
Empowering everyone to build reliable and efficient software.
Announcing Rust 1.96.1 | Rust Blog
Empowering everyone to build reliable and efficient software.
One year of Rust | Rust Blog
Empowering everyone to build reliable and efficient software.
Zig 2026: No-AI Policy, $670K Foundation, Left GitHub & Why Zig Isn’t 1.0 - Andrew Kelley Explains
Why Zig When There is Already C++, D, and Rust? ⚡ Zig Programming Language
If Zig code doesn’t look like it’s jumping away to call a function, then it isn’t. This means you can be sure that the following code calls only foo() and then bar(), and this is guaranteed without needing to know the types of anything:
Rust in 2021
This is my response for this year's call for blog posts. I am writing this as a language implementor, not as a language user. I also don't try to prioritize the problems. The two things I'll mention are the things that worry me most without reflecting on the overall state of the project. They are not necessary the most important things.
The Evolution of a Rust Programmer
364 votes, 71 comments. 426K subscribers in the rust community. A place for all things related to the Rust programming language—an open-source…
RustFest Interviews Triple Feature: Rust for AAA Game Development; Async Foundations with `async-std`; and Powerful Concurrency Primitives with `crossbeam` :: Rustacean Station
Come journey with us into the weird, wonderful, and wily world of Rust.
Inside Zig's Incremental Compilation
As a member of the Zig core team, one of the most impactful projects I’ve been involved with is the implementation of incremental compilation into the Zig compiler. This feature allows the compiler to detect which individual functions and declarations have changed since a project was last built, recompile only that code, and directly patch the resulting bytes into the output binary, making the rebuild extremely fast.
Is It Time to Rewrite the Operating System in Rust?
Bryan Cantrill explores Rust, explains why it has captured the imagination of so many systems software engineers, and outlines where it might best fit in the deep stack of operating system software.
Systems Programming with Zig
Zig delivers performance, reliability, and complex integration in systems programming in a simple, modern package. Zig hits the sweet spot for systems programming. This new programming language is high-performance, low-level, ultra-reliable, and perfectly suited for serious projects like writing libraries, daemons and shell utilities, and even operating systems and embedded code. Systems Programming with Zig shows you how to write quality, useful Zig applications without relying on libraries or frameworks-even if you’re new systems programming. In Systems Programming with Zig you’ll learn how to: Understand the Zig perspective on systems programming Write idiomatic Zig code Integrate Zig with C, systems libraries, and scripting languages Networking, interpreters, and graphics from the ground up Unlike UI-centric applications that form the public face of your software, systems programs like OS kernels, device drivers, and utilities interact directly with the hardware or operating system. In these low-level programs, performance and safety are paramount. Zig is a new programming language that builds on the legacy of C, C++, and even Rust to provide a high-productivity systems programming environment that does not rely on awkward libraries and frameworks.
lambek - Rust
Lambek is a library that enables type-level programming in stable Rust, supporting advanced features including higher kinded types, higher ranked types, and constraint kinds. Although Rust do not natively support these features, Lambek uses techniques including defunctionalization and CPS transformation to emulate these features in Rust.
Refining Rust's RFCs · Aaron Turon
At the heart of Rust’s open development is the RFC process. Every major change to the language, compiler, core libraries, tooling, and policy go through an RFC writeup and consensus-building process. The process served us incredibly well in clarifying our technical direction on the road to 1.0, and has continued to be highly active since then, with on average about 2 RFCs merged every week.