@jberanek.bsky.social
Blogged about what I have been up to lately in upstream Rust.
Sovereign Tech Fellowship for Rust maintenance (June-July 2026 report)
For the past few years, I was sponsored by Futurewei to work on upstream Rust. It was great to have the freedom to work on anything I wanted in Rust, be it new features, performance optimizations, bot...
kobzol.github.io
It is time for the annual State of Rust Survey! 📝✨️️ Whether you've just begun using Rust, are an experienced Rust user, stopped using Rust, or might use Rust in the future, we'd like to hear from you! 🦀 Available in ten languages and open until December 17th: blog.rust-lang.org/2025/11/17/l...
Launching the 2025 State of Rust Survey | Rust Blog
Empowering everyone to build reliable and efficient software.
blog.rust-lang.org
Proposed and implemented a new feature to Rust (#[derive(From)]) - you can read about it here: kobzol.github.io/rust/2025/09...
Adding #[derive(From)] to Rust
TL;DR: #[derive(From)] can be used in nightly now. See here on how to use it. You can follow this tracking issue for more updates.
kobzol.github.io
See how Rust compiler error messages have evolved over time :) kobzol.github.io/rust/rustc/2...
Evolution of Rust compiler errors
Blog about programming stuff.
kobzol.github.io
Wrote down some thoughts on how to interpret and use visibility in Rust. kobzol.github.io/rust/2025/04...
Two ways of interpreting visibility in Rust
Last year, while I was browsing through Rust compiler pull requests, I noticed #126013, which added the unreachable_pub lint to several crates of the compiler. This piqued my interest, because I did n...
kobzol.github.io
