baby steps

The Async Vision Doc effort has been going now for about 6 weeks.

My week is very scheduled, so I am not able to host any public drafting sessions this week – however, Ryan Levick will be hosting two sessions!

Ryan Levick and I are going to be hosting more Async Vision Doc Writing Sessions this week.

This is an exciting week for the vision doc!

My week is very scheduled, so I am not able to host any public drafting sessions this week – however, Ryan Levick will be hosting two sessions!

I’ve been working on the Rust project for just about ten years.

Ryan Levick and I are hosting a number of public drafting sessions scheduled this week.

I’m scheduling two more public drafting sessions for tomorrow, Match 26th: On March 26th at 10am ET (click to see in your local timezone), we will be working on writing a story about the challenges of writing a library that can be reused across many runti…

Hey folks!

I’ve got an announcement to make.

I wanted to write a post that looks back over 2020 from a personal perspective.

Since we created the Rust teams, I have been serving as lead of two teams: the compiler team and the language design team (I’ve also been a member of the core team, which has no lead).

(removed)

The point of the async interview series, in the end, was to help figure out what we should be doing next when it comes to Async I/O.

I’ve noticed that the ideas that I post on my blog are getting much more “well rounded”.

Hello everyone!

Hello!

Hello!

Hello!

In my #rust2020 blog post, I mentioned rather off-handedly that I think the time has come for us to talk about forming a Rust foundation.

Hello!

This blog post is continuing my conversation with cramertj.

This blog post is continuing my conversation with cramertj.

For the second async interview, I spoke with Taylor Cramer – or cramertj, as I’ll refer to him. cramertj is a member of the compiler and lang teams and was – until recently – working on Fuchsia at Google.

I want to write about an idea that Josh Triplett and I have been iterating on to revamp the lang team RFC process.

Technically speaking, it’s past the deadline for #rust2020 posts, but I’m running late this year, and I’m going to post something anyway.

Hello from Iceland!

Hello all!

After reading boat’s excellent post on asynchronous destructors, I thought it might be a good idea to write some about async fn in traits.

I would like to describe an idea that’s been kicking around in my head.

I have been thinking about how language feature development works in Rust1.

I wanted to give an update on the status of the “async-await foundations” working group.

On internals, I just announced the formation of the language-design team meta working group.

In my previous post, I talked about the idea of mapping the solution space: When we talk about the RFC process, we always emphasize that the point of RFC discussion is not to select the best answer; rather, the point is to map the solution space.

In the talk I gave at Rust LATAM, I said that the Rust project has always emphasized finding the best solution, rather than winning the argument.

Lately, the compiler team has been changing up the way that we work.

I wanted to post a quick update on the status of the async-await effort.

Now that the Rust 2018 edition has shipped, the language design team has been thinking a lot about what to do in 2019 and over the next few years.

So for the last couple of months or so, I’ve been hacking in my spare time on this library named salsa, along with a number of awesome other folks.

In my previous post about Polonius and subregion obligations, I mentioned that there needs to be a follow-up to deal with higher-ranked subregions.

Now that NLL has been shipped, I’ve been doing some work revisiting the Polonius project.

To me, 2018 felt like a big turning point for Rust, and it wasn’t just the edition.

Continuing on with my “After NLL” series, I want to look at another common error that I see and its solution: today’s choice is about moves from borrowed data and the Sentinel Pattern that can be used to enable them.

This week I’ve been attending SPLASH 2018.

In my previous post on the status of NLL, I promised to talk about “What is next?”

Now that the final Rust 2018 Release Candidate has shipped, I thought it would be a good idea to do another update on the state of the MIR-based borrow check (aka NLL).

Just a quick note that the October 2018 office hour slots are now posted.

This is a report on the second “office hours”, in which we discussed how to setup a series of services or actors that communicate with one another.

This is a report on the first “office hours”, in which we discussed debugging Rust programs with gdb.

Hello, all!