What happened is that we created a self-referential struct, initialized it so that it took a pointer to itself, and then moved it. Let’s take a closer look: You’ve now

Pretend you haven’t read this section title and enjoy the fact that our previous example compiled and showed the correct result. I think our coroutine implementation is so good now

Yes, I know we could have chosen another way of doing this since we can take a reference to buffer everywhere we need to instead of storing it in its

Let’s set everything up for our next version of this example: Note You can find this example in this book’s GitHub repository in the ch10/b-coroutines-references folder. This time, we’ll learn

Futures created by async/await in Rust store this data in a slightly more efficient manner. In our example, we store every variable in a separate struct since I think it’s

We want to see how we can improve our state machine so that it allows us to hold variables across wait points. To do that, we need to store them

So, let’s recap what we have at this point by continuing where we left off in the previous chapter. We have the following: It’s not that bad – we might

In this chapter, we’ll start by improving our coroutines by adding the ability to store variables across state changes. We’ll see how this leads to our coroutines needing to take