rust-lang / rust-lang/impl-trait-utils
Is there a plan for this crate?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 134
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue text and its six-comment discussion, focusing on the async-trait transition and the proposed boxed or unboxed behavior. Check the unresolved work referenced in the discussion; this issue is complete only when the project direction and next steps are decided and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100