baby steps

Lately I’ve been thinking about cyclic trait implementations.

This blog post describes an idea I’ve been kicking around called battery packs.

only bounds are going to be the most impactful change to Rust that you’ve never heard of.

I’m very excited to announce the first release of the Symposium project as well as its inclusion in the Rust Foundation’s Innovation Lab.

A short post to catalog two interesting suggestions that came in from my previous post, and some other related musings.

This blog post describes a maximally minimal proposal for view types.

In my previous Dada blog post, I talked about how Dada enables composable sharing.

Righty-ho, I’m back from Rust Nation, and busily horrifying my teenage daughter with my (admittedly atrocious) attempts at doing an English accent1.

OK, let’s talk about sharing.

Let’s continue with working through Dada.

Following on my Fun with Dada post, this post is going to start teaching Dada.

Waaaaaay back in 2021, I started experimenting with a new programming language I call “Dada”.

This post explores another proposal in the space of ergonomic ref-counting that I am calling move expressions.

Continuing my series on ergonomic ref-counting, I want to explore another idea, one that I’m calling “just call clone (or alias)”.

Hmm, as I re-read the post I literally just posted a few minutes ago, I got to thinking.

There have been two major sets of responses to my proposal for a Handle trait.

In my previous post about Ergonomic Ref Counting, I talked about how, whatever else we do, we need a way to have explicit handle creation that is ergonomic.

This post presents a proposal to extend Rust to support a number of different kinds of destructors.

Continuing my discussion on Ergonomic RC, I want to focus on the core question: should users have to explicitly invoke handle/clone, or not?

This post describes SymmACP – a proposed extension to Zed’s Agent Client Protocol that lets you build AI tools like Unix pipes or browser extensions.

There’s been a lot of discussion lately around ergonomic ref-counting.

This blog post gives you a tour of Symposium, a wild-and-crazy project that I’ve been obsessed with over the last month or so.

You heard it here first: my guess is that Rust, Python, and TypeScript are going to become the dominant languages going forward (excluding the mobile market, which has extra wrinkles).

Recently someone forwarded me a PCMag article entitled “Vibe coding fiasco” about an AI agent that “went rogue”, deleting a company’s entire database.

Just yesterday, AWS announced General Availability for a cool new service called Aurora DSQL – from the outside, it looks like a SQL database, but it is fully serverless, meaning that you never have to think about managing database instances, you pay for…

Today is the 10th anniversary of Rust’s 1.0 release.

Knock, knock.

This article is a slight divergence from my Rust in 2025 series.

For many years, C has effectively been the “lingua franca” of the computing world.

Rust turns 10 this year.

A few years back I proposed view types as an extension to Rust’s type system to let us address the problem of (false) inter-procedural borrow conflicts.

So, a little bird told me that Rust 2024 is going to become stable today, along with Rust 1.85.0.

I believe that AI-powered development tools can be a game changer for Rust—and vice versa.

This post lays out the idea of preview crates.1 Preview crates would be special crates released by the rust-lang org.

This post floats a variation of boats’ UnpinCell proposal that I’m calling MinPin.1 MinPin’s goal is to integrate Pin into the language in a “minimally disruptive” way2 – and in particular a way that is fully backwards compatible.

In July, boats presented a compelling vision in their post pinned places.

What would you say if I told you that it was possible to (a) eliminate a lot of “inter-method borrow conflicts” without introducing something like view types and (b) make pinning easier even than boats’s pinned places proposal, all without needing pinned…

This is the first of what I think will be several follow-up posts to “Claiming, auto and otherwise”.

This blog post proposes adding a third trait, Claim, that would live alongside Copy and Clone.

This post lays out a 4-part roadmap for the borrow checker that I call “the borrow checker within”.

I’ve been thinking a wild thought lately: we should deprecate panic=unwind.

Extern types have been blocked for an unreasonably long time on a fairly narrow, specialized question: Rust today divides all types into two categories — sized, whose size can be statically computed, and unsized, whose size can only be computed at runtime.

Ownership is an important concept in Rust — but I’m not talking about the type system.

This blog post explores an alternative formulation of Rust’s type system that eschews lifetimes in favor of places.

Well, it’s that time of year, when thoughts turn to…well, Rust of course.

To your average Joe, being “rusty” is not seen as a good thing.1 But readers of this blog know that being Rusty – with a capitol R!

Lately I’ve been iterating on an idea I call project goals.

A few years back, the Async Wg tried something new.

I’m on the plane back to the US from Belgium now and feeling grateful for having had the chance to speak at the EuroRust conference1.

Rust helps you to build reliable programs.