Replace cap-async-std

Open
#408 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
backend

Research direction

Start by reviewing the removal described in pull request #399 and the repository's former cap-async-std crate context. Compare the proposed cap-tokio and cap-smol directions, then confirm the replacement restores async functionality without relying on async-std; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

cap-async-std has been removed without a replacement (see https://github.com/bytecodealliance/cap-std/pull/399), because async-std is no longer maintained.
Now there is no way of using async code with this crate.

It would make sense to add either a:

  • cap-tokio (I would prefer this one)

or a

  • cap-smol

crate to this repository to retain the async functionality of this project.

Dominant language
Rust
Stars
821
Forks
59
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/cap-std

All issues in bytecodealliance/cap-std

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.