Creating a proper runtime 185 Figure 8. 6-A loosely coupled reactor and executor It's no coincidence that we land on the same design as what we have in Rust today. It's a minimal design from Rust's point of view, but it allows for a wide variety of runtime designs without laying too many restrictions for the future. Note Even though the design is pretty minimal today from a language perspective, there are plans to stabilize more async-related traits and interfaces in the future. Rust has a working group tasked with including widely used traits and interfaces in the standard library, which you can find more information about here: https://rust-lang. github. io/wg-async/welcome. html. Y ou can also get an overview of items they work on and track their progress here: https://github. com/orgs/rust-lang/projects/28/ views/1. Maybe you even want to get involved ( https://rust-lang. github. io/wg-async/ welcome. html#-getting-involved ) in making async Rust better for everyone after reading this book? If we change our system diagram to reflect the changes we need to make to our runtime going forward, it will look like this: 