Skip to content
A point of coordination for all things Rust and Async
Branch: master
Clone or download
Bastian Gruber
Bastian Gruber Merge pull request #134 from gruberb/20190718
Add todays meeting minutes
Latest commit f4efed8 Jul 22, 2019

Rust 2019 Async Ecosystem Working Group

This repo is for coordinating the Rust Async Ecosystem Working Group.

The issue tracker on this repo is a primary point of coordination. If you have an async-related topic you'd like to raise, please feel free to open an issue!

Goals and structure

The WG is focused on progressing the ecosystem around the async foundations in 2019. If you want to get involved in these efforts, hop on Discord and say hello, or take a look at the issue tracker. Our goal is to improve the async library ecosystem in Rust by:

  • Bolstering web components, i.e. assessing the state of foundational crates for web programming (like http and url), and working to improve it by writing documentation and examples, making API improvements, standardizing interfaces, and in some cases writing whole new crates.
  • Building Tide, which is a combination of a simple, modular web framework built on the above components, and extensive documentation on what the components are, how to use them directly, and how they integrate into a framework. The name "Tide" refers to "a rising tide lifts all boats", conveying the intent that this work is aimed to improve sharing, compatibility, and improvements across all web development and frameworks in Rust.
  • Experimenting with projects such as the Juliex executor, the Romio reactor, and the Runtime crate
  • The Asynchronous Programming in Rust book should have a complete draft, covering async/await, core futures concepts, Tokio, and enough of the ecosystem to give good examples and guidance. It should also explicitly talk about the stabilization situation, including how to bridge between stable 0.1 and unstable 0.3 worlds.
You can’t perform that action at this time.