Skip to content

Is there a plan for this crate? #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sytten opened this issue Jun 24, 2024 · 6 comments
Open

Is there a plan for this crate? #35

Sytten opened this issue Jun 24, 2024 · 6 comments

Comments

@Sytten
Copy link

Sytten commented Jun 24, 2024

Hi!

It has been some time that async trait have been released. Some crates have moved to it, but for some people the transition is not easy. It would be great if we could easy replace async-trait with something that can be boxed or not depending on a feature flag for example.

This crate was kinda of the promise of the partial async trait release but it seemed to have lost interest or focus. Important PR are in limbo and it clearly isn't getting a lot of community adoption/love.

So what's the plan here? Is this crate still important for the async WG or not?

I hope I don't sound harsh and I appreciate the hard work put into it, I am really just trying to see what are the next steps.

Best

@tmandry
Copy link
Member

tmandry commented Jul 30, 2024

@Sytten thanks for your question.

@spastorino is working on support for dyn dispatch which should close the major remaining use case gap between this crate and async-trait.

I am willing to review PRs but unfortunately haven't done a good job of responding to activity on this repo. I'm more likely to respond to Zulip pings.

@Sytten
Copy link
Author

Sytten commented Aug 15, 2024

Thanks for the update @tmandry hopefully we can make it more complete and start driving the community towards it. I have not seen a single crate use it at the moment.

@matthew-russo
Copy link

matthew-russo commented Jan 3, 2025

Any update? Seems like there hasn't been any activity in this repo

@Sytten
Copy link
Author

Sytten commented Jan 3, 2025

As far as I am aware this crate is more or less dead. Kinda of shame since there is really no good solution right now if you want to slowly transition out of async-trait, I had to do a bunch of ugly hacks in async-graphql.

I guess the limited async WG resources ate better spent finding a native solution to the many problems this crate was supposed to patch (Send, Boxed, etc)

@matthew-russo
Copy link

Gotcha, thanks. I'll figure out something else then

@spastorino
Copy link
Member

@Sytten thanks for your question.

@spastorino is working on support for dyn dispatch which should close the major remaining use case gap between this crate and async-trait.

I am willing to review PRs but unfortunately haven't done a good job of responding to activity on this repo. I'm more likely to respond to Zulip pings.

I just saw that @tmandry mentioned that I'm working on support for dyn dispatch. Just in case people find this out, the work I've done lives in https://github.com/spastorino/dynosaur

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants