async-fundamentals-initiative's Introduction

async fundamentals initiative

What is this?

This page tracks the work of the async fundamentals initiative, part of the wg-async-foundations vision process! To learn more about what we are trying to do, and to find out the people who are doing it, take a look at the charter.

Current status

This is an umbrella initiative and, as such, it covers a number of subprojects.

See the roadmap for a list of individual milestones and their status.

Subproject	Issue	Progress	State	Status
async fn	#50547	▰▰▰▰▰	✅	![stable][]
static async fn in trait	#91611	▰▰▱▱▱	🦀	![accepted rfc][]
dyn async fn in trait	–	▰▱▱▱▱	🦀	![planning rfc][]
async drop	–	▰▱▱▱▱	🦀	![not started][]
async closures	–	▰▱▱▱▱	💤	![not started][]

Key:

✅ – phase complete
🦀 – phase in progress
💤 – phase not started yet

How Can I Get Involved?

Check for 'help wanted' issues on this repository!
If you would like to help with development, please contact the owner to find out if there are things that need doing.
If you would like to help with the design, check the list of active design discussions first.
If you have questions about the design, you can file an issue, but be sure to check the FAQ or the design discussions first to see if there is already something that covers your topic.
If you are using the feature and would like to provide feedback about your experiences, please open a "experience report" issue.
If you are using the feature and would like to report a bug, please open a regular issue.

We also participate on Zulip, feel free to introduce yourself over there and ask us any questions you have.

Building Documentation

This repository is also an mdbook project. You can view and build it using the following command.

mdbook serve

async-fundamentals-initiative's People

Contributors

Stargazers

Watchers

async-fundamentals-initiative's Issues

Async fn in traits initiative

Metadata
Name	Async fns in traits initiative
Owner	@tmandry
Liaison	@joshtriplett
Proposed in	rust-lang/lang-team#150

Purpose

Working towards support for

trait Foo {
    async fn bar(&self);
}

Artifacts

Accepted RFC: Static async fn in traits (rust-lang/rfcs#3185)

Attributes to indicate Send/Sync bound for Future generated in Static Async Trait

Motivation

As previously discussed it's a debated issue how to express Send/Sync bounds on the generated associated types for async methods. As I understand it, this issue will be resolved in the future. I'm currently writing a library which might profit from a way to express the bound so I would appreciate a solution for the problem to be stabilized along with static-async-trait.

Details

I'm currently developing a macro library that tries to implement about the same desugaring as described in the RFC. I came up with a solution for this using attributes on the trait methods.

Example

struct Foo;

trait Bar {
    #[send]
    async fn wait(&self);
}

impl Bar for Foo {
    async fn wait(&self) {
        todo!()
    }
}

// this trait can now be used with tokio::spawn
async fn spawn_trait<T: Bar + Sync + Send + 'static>(foo: T) {
    let handle = tokio::spawn(async move {
        foo.wait().await;
    });
    handle.await;
}

A method with a body that has to be Send is just annotated with #[send] and for Sync it's just annotated with #[sync].

An attribute would not be that unusual. Derive default enum uses an attribute as well.

Caveats

How would this appear in rustdoc?

I would appreciate your feedback

Recommend Projects

rust-lang / async-fundamentals-initiative Goto Github PK