baby steps

In the previous Polonius post, we formulated the original borrow checker in a Polonius-like style.

Over the last few weeks I had been preparing a talk on “Inclusive Mentoring: Mentoring Across Differences” with one of my good friends at Amazon.

lqd has been doing awesome work driving progress on polonius.

Some time ago I wrote about how I wanted to improve how my blog works.

One of Rust’s core principles is “stability without stagnation”.

I recently posted a draft of an RFC about Return Type Notation to the async working group Zulip stream.

In a previous post on async closures, I concluded that the best way to support async closures was with an async trait combinator.

It’s well known that my blog has some issues.

I’ve been thinking about async closures and how they could work once we have static async fn in trait.

Rust has lots of mechanisms that prevent you from doing something bad.

In today’s lang team design meeting, we reviewed a doc I wrote about temporary lifetimes in Rust.

One interesting question about async fn in traits is whether or not we should label the trait itself as async.

I previously introduced the “send bound” problem, which refers to the need to add a Send bound to the future returned by an async function.

In the previous post, I introduced the “send bound” problem, which refers to the need to add a Send bound to the future returned by an async function.

Nightly Rust now has support for async functions in traits, so long as you limit yourself to static dispatch.

When I started working on Rust in 2011, my daughter was about three months old.

I’ve been thinking about what “Rust 2024” will look like lately.

After my last post on dyn async traits, some folks pointed out that I was overlooking a seemingly obvious possibility.

Re-reading my previous post, I felt I should clarify why I called it the “soul of Rust”.

In the last few months, Tyler Mandry and I have been circulating a “User’s Guide from the Future” that describes our current proposed design for async functions in traits.

Have you heard of the Salsa project?

As some of you may know, on May 4th Jack Huey opened a PR to stabilize an initial version of generic associated types.

You’ve probably heard that the Rust type checker can be a great “co-pilot”, helping you to avoid subtle bugs that would have been a royal pain in the !

Lately I’ve been diving deep into tokio’s mini-redis example.

Rust has been wrestling with coherence more-or-less since we added methods; our current rule, the “orphan rule”, is safe but overly strict.

There are two ergonomic features that have been discussed for quite some time in Rust land: perfect derive and expanded implied bounds.

Last Friday, tmandry, cramertj, and I had an exciting conversation.

Last year, we shipped Rust 2021 and I have found the changes to be a real improvement in usability.

One of the things people often complain about when doing Async Rust is cancellation.

Hi all!

Wow!

The next “Cross Team Collaboration Fun Times” (CTCFT) meeting will take place next Monday, on 2021-11-22 at 11am US Eastern Time (click to see in your time zone).

I wanted to write about an idea that’s been kicking around in the back of my mind for some time.

Ever wanted to understand how rustc works?

A quick update to my last post: first, a better way to do what I was trying to do, and second, a sketch of the crate I’d like to see for experimental purposes.

If you’re willing to use nightly, you can already model async functions in traits by using GATs and impl Trait — this is what the Embassy async runtime does, and it’s also what the real-async-trait crate does.

The next “Cross Team Collaboration Fun Times” (CTCFT) meeting will take place next Monday, on 2021-10-18 (in your time zone)!

In the previous post, I talked about how we could write our own impl Iterator for dyn Iterator by adding a few primitives.

In the previous “dyn async traits” posts, I talked about how we can think about the compiler as synthesizing an impl that performed the dynamic dispatch.

In the previous post, we uncovered a key challenge for dyn and async traits: the fact that, in Rust today, dyn types have to specify the values for all associated types.

Over the last few weeks, Tyler Mandry and I have been digging hard into what it will take to implement async fn in traits.

RustConf is always a good time for reflecting on the project.

The next “Cross Team Collaboration Fun Times” (CTCFT) meeting will take place next Monday, on 2021-09-20 (in your time zone)!

As the web site says, Rust is a language empowering everyone to build reliable and efficient software.

Hold the date!

The next “Cross Team Collaboration Fun Times” (CTCFT) meeting will take place one week from today, on 2021-07-19 (in your time zone)!

Hey everyone!

The second “Cross Team Collaboration Fun Times” (CTCFT) meeting will take place one week from today, on 2021-06-21 (in your time zone)!

You may have heard that the Rust 2021 Edition is coming.

This Monday I am starting something new: a monthly meeting called the “Cross Team Collaboration Fun Times” (CTCFT)1.