Excited to share Google's memory safety strategy! We're working to build safer software by migrating to memory-safe languages like Rust as well as hardening our existing C++: security.googleblog.com/2024/10/safer-…. We'll be sharing more details in upcoming posts.

Excited to share our latest post on memory safety! We're tackling spatial safety in our massive C++ codebase by hardening libc++ *by default*. It adds bounds checks to things like std::vector, preventing a fair bit of out-of-bounds vulnerabilities: security.googleblog.com/2024/11/retrof…

The "Rust syntax is not that bad" people have not yet discovered that the expression `x = y + ..` parses as `x = (y + ..)` while the expression `x = .. + y` parses as `(x = ..) + y`. In other languages, the precedence of an operator depends on that operator. So it makes sense to

Evidence that "async functions in traits" (Rust 1.75+) is successfully displacing usage of the old `async-trait` crate at ecosystem scale. Expect a second clear inflection point when async works natively in `dyn Trait`.

The variation I've gotten is: "highly competitive compensation package" … offers 7-figure pay cut.

What did I do in December in rustc? hackmd.io/@compiler-erro…

In working on the next ZIO Schema, I took a look at Rust serde, a really excellent library that is radically different than Schema, but accomplishes the same primary goal (cross-format serialization and deserialization). ZIO Schema's operating principle is that your type A can

Not long ago, I used to have a more optimistic impression of Rust users. I would not have guessed that so many otherwise-judicious people would go for blatantly AI-"maintained" Rust libraries. The `serde_yml` crate is a fork of a high-quality but unmaintained library. In the

We’re building a new static type checker for Python, from scratch, in Rust. From a technical perspective, it’s probably our most ambitious project yet. We’re about 800 PRs deep!

New question #37 on the Rust Quiz, contributed by GitHub user ChayimFriedman2. dtolnay.github.io/rust-quiz/37

Disabling LSP autocompletions in my editor has been the most productivity enhancing thing I've done. It's actually insane. I do sometimes do C-x to trigger and see a list of methods, but that's when I want to check if there's a better way. It has made me a better programmer.

jiff 0.2 is out! There are several breaking changes (although the overall API organization remains unchanged). This release also comes with new crates for integrating with ICU4X, SQLx and Diesel. github.com/BurntSushi/jif…

Career advice for an ambitious infrastructure engineer like me: find the world's largest Rust codebase and solve their hard problems. My team is hiring a senior engineer to work closely with me. In simple form, the job is: show up to an office in NYC, Seattle, Bellevue, or Menlo

David Tolnay "medium-sized Rust codebase (10 million lines)" lfg

One of the most surprising conserved quantities in the Rust ecosystem: over a span of 10 years, the fraction of crates with a transitive dependency on libc remains 55% ± 2pp.

5-year reality check: directly depended on by 20% of crates and still climbing rapidly. Hopefully this motivates standardizing most of the functionality of these 2 crates into standard library #[derive(Display)] and #[derive(Error)] and a good anyhow::Error-equivalent type.

Bad news -- I'm not going to be with my employer for much longer due to team relocation demands. If anyone has any leads for roles that would allow me to continue my Rust compiler work (in New York City), they'd be greatly appreciated.