Note Even though we create a runtime to run futures properly in Rust, we still try to keep this simple by avoiding error handling and not focusing on making our

In the last few chapters, we covered a lot of aspects that are relevant to asynchronous programming in Rust, but we did that by implementing alternative and simpler abstractions than

What a ride, huh? If you’ve got to the end of this chapter, you’ve done a fantastic job, and I have good news for you: you pretty much know everything

The first thing we must do is make sure our dependencies are correct. The only change we’re making here is adding Pin from the standard library: ch09/e-coroutines-pin/src/runtime/executor.rs…    thread::{self, Thread},pin::Pin,};  The next

The first thing we need to do is pull in Pin from the standard library. The start of the file should look like this: ch09/e-coroutines-pin/src/http.rsuse crate::{future::PollState, runtime::{self, reactor, Waker}, Future};use

Before we leave the topic of pinning, we’ll quickly explain what pin projections and structural pinning are. Both sound complex, but they are very simple in practice. The following diagram

Pinning to the stack can be somewhat difficult. In Chapter 5, we saw how the stack worked and we know that it grows and shrinks as values are popped and

Note The small code snippets we’ll present here can be found in this book’s GitHub repository in the ch09/d-pin folder. The different examples are implemented as different methods that you

The following diagram shows a slightly more complex self-referential struct so that we have something visual to help us understand: Figure 9.3 – Moving a self-referential struct with three fields

A move in Rust is one of those concepts that’s unfamiliar to many programmers coming from C#, Javascript, and similar garbage-collected languages, and different from what you’re used to for