[PR #2867] [MERGED] Remove support for async-std #3380

Closed
opened 2026-03-16 11:40:39 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/2867
Author: @djc
Created: 3/17/2025
Status: Merged
Merged: 3/18/2025
Merged by: @djc

Base: mainHead: rm-async-std


📝 Commits (1)

  • 72a6011 Remove support for async-std

📊 Changes

12 files changed (+29 additions, -754 deletions)

View changed files

📝 .github/workflows/test.yml (+0 -1)
📝 CHANGELOG.md (+2 -2)
📝 Cargo.lock (+25 -315)
📝 Cargo.toml (+0 -1)
📝 crates/proto/Cargo.toml (+0 -3)
crates/proto/src/async_std.rs (+0 -243)
📝 crates/proto/src/lib.rs (+0 -2)
📝 crates/resolver/Cargo.toml (+0 -2)
crates/resolver/src/async_std.rs (+0 -178)
📝 crates/resolver/src/lib.rs (+0 -2)
📝 crates/resolver/src/resolver.rs (+1 -1)
📝 justfile (+1 -4)

📄 Description

The async-std README now has the following notice:

async-std has been discontinued; use smol instead

We created async-std to demonstrate the value of making a library as close to std as possible, but async. We think that demonstration was successful, and we hope it will influence future design and development directions of async in std. However, in the meantime, the smol project came about and provided a great executor and libraries for asynchronous use in the Rust ecosystem. We think that resources would be better spent consolidating around smol, rather than continuing to provide occasional maintenance of async-std. As such, we recommend that all users of async-std, and all libraries built on async-std, switch to smol instead.

In addition to the smol project as a direct replacement, you may find other parts of the futures ecosystem useful, including futures-concurrency, async-io, futures-lite, and async-compat.

Since we're on the cusp of a semver-incompatible release anyway, let's tear this out. Can always add it back if someone really wants it (they could also maintain it externally AFAICT).


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/2867 **Author:** [@djc](https://github.com/djc) **Created:** 3/17/2025 **Status:** ✅ Merged **Merged:** 3/18/2025 **Merged by:** [@djc](https://github.com/djc) **Base:** `main` ← **Head:** `rm-async-std` --- ### 📝 Commits (1) - [`72a6011`](https://github.com/hickory-dns/hickory-dns/commit/72a601157d7b6c3462caa64842c7a5cd5798cc42) Remove support for async-std ### 📊 Changes **12 files changed** (+29 additions, -754 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/test.yml` (+0 -1) 📝 `CHANGELOG.md` (+2 -2) 📝 `Cargo.lock` (+25 -315) 📝 `Cargo.toml` (+0 -1) 📝 `crates/proto/Cargo.toml` (+0 -3) ➖ `crates/proto/src/async_std.rs` (+0 -243) 📝 `crates/proto/src/lib.rs` (+0 -2) 📝 `crates/resolver/Cargo.toml` (+0 -2) ➖ `crates/resolver/src/async_std.rs` (+0 -178) 📝 `crates/resolver/src/lib.rs` (+0 -2) 📝 `crates/resolver/src/resolver.rs` (+1 -1) 📝 `justfile` (+1 -4) </details> ### 📄 Description The async-std README now has the following notice: > ## async-std has been discontinued; use smol instead > > We created async-std to demonstrate the value of making a library as close to std as possible, but async. We think that demonstration was successful, and we hope it will influence future design and development directions of async in std. However, in the meantime, the [smol](https://github.com/smol-rs/smol/) project came about and provided a great executor and libraries for asynchronous use in the Rust ecosystem. We think that resources would be better spent consolidating around smol, rather than continuing to provide occasional maintenance of async-std. As such, we recommend that all users of async-std, and all libraries built on async-std, switch to smol instead. > > In addition to the smol project as a direct replacement, you may find other parts of the futures ecosystem useful, including futures-concurrency, async-io, futures-lite, and async-compat. Since we're on the cusp of a semver-incompatible release anyway, let's tear this out. Can always add it back if someone really wants it (they could also maintain it externally AFAICT). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-16 11:40:39 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#3380
No description provided.