Skip to content
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

Prefer tokio runtime everywhere #4449

Open
Tracked by #3515
thomaseizinger opened this issue Sep 5, 2023 · 0 comments
Open
Tracked by #3515

Prefer tokio runtime everywhere #4449

thomaseizinger opened this issue Sep 5, 2023 · 0 comments

Comments

@thomaseizinger
Copy link
Contributor

Description

Historically, examples and tests in rust-libp2p have used a mix of the async-std and tokio runtime. These days, both runtimes are equally well supported by the library but the examples and tests are still mixed. For now, we want to keep supporting async-std but all examples and tests should use the tokio runtime.

Motivation

The tokio runtime is much more well established and better maintained. Users should be able to use other runtimes or bring their own.

Current Implementation

Both runtimes are being mixed.

mergify bot pushed a commit that referenced this issue Sep 23, 2023
mergify bot pushed a commit that referenced this issue Oct 1, 2023
Changed the `autonat` example to use `tokio` instead of `async-std` as runtime.

Related: #4449.

Pull-Request: #4574.
mergify bot pushed a commit that referenced this issue Oct 3, 2023
mergify bot pushed a commit that referenced this issue Oct 4, 2023
mergify bot pushed a commit that referenced this issue Oct 5, 2023
mergify bot pushed a commit that referenced this issue Feb 29, 2024
guillaumemichel pushed a commit that referenced this issue Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant