Skip to content

async-std deprecation message not sufficiently advertised #1102

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
harmic opened this issue May 1, 2025 · 0 comments
Open

async-std deprecation message not sufficiently advertised #1102

harmic opened this issue May 1, 2025 · 0 comments

Comments

@harmic
Copy link

harmic commented May 1, 2025

The recent deprecation message committed to this repo appears in the README and as a consequence on crates.io, but it does not appear:

Given the name of this package & the slick home page it is likely that people stumbling on one of the above two resources will think async-std is a semi-official crate and a good choice for a new project.

It could also be good to add #![deprecated(since="1.13.1",note="some message")] to the main lib.rs. That would result in deprecation warnings at compile time. Unfortunately you get one warning per reference to anything used from the crate - I would rather get a single warning to say the whole crate is deprecated, but I can't see any way to do that.

I also have some reservations about a blanket recommendation to switch to smol. While I am sure that smol is great, the fact is that tokio is far more widely used & supported, and like it or not is the defacto standard async runtime. It would be fairer to developers who are faced with the need to switch runtimes to at least list the main alternatives.

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

1 participant