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

Drop async-std crate #179

Merged

Conversation

sophie-h
Copy link
Contributor

The async-std crate didn't had a release for 1 1/2 years. It also pulls in a lot of dependencies that are usually not needed. The Path::exists() feature of async-std is just using spawn_blocking around the std metadata function and therefore settling on a specific executor and spawning a bunch of threads that might not be needed.

Therefore I replaced all uses of async-std with the crates from which async-std is build and that are well maintained.

The async-std crate didn't had a release for 1 1/2 years. It also pulls in
a lot of dependencies that are usually not needed. The Path::exists()
feature of async-std is just using spawn_blocking around the std
metadata function and therefore settling on a specific executor and
spawning a bunch of threads that might not be needed.

Therefore I replaced all uses of async-std with the crates from which
async-std is build and that are well maintained.
@bilelmoussaoui bilelmoussaoui merged commit 6576a33 into bilelmoussaoui:master Jan 6, 2024
5 of 6 checks passed
@bilelmoussaoui
Copy link
Owner

thanks!

bilelmoussaoui pushed a commit that referenced this pull request Jan 6, 2024
The async-std crate didn't had a release for 1 1/2 years. It also pulls in
a lot of dependencies that are usually not needed. The Path::exists()
feature of async-std is just using spawn_blocking around the std
metadata function and therefore settling on a specific executor and
spawning a bunch of threads that might not be needed.

Therefore I replaced all uses of async-std with the crates from which
async-std is build and that are well maintained.
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

Successfully merging this pull request may close these issues.

2 participants