Skip to content

Removed obligatory async-std dep #168

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

Closed
wants to merge 2 commits into from
Closed

Removed obligatory async-std dep #168

wants to merge 2 commits into from

Conversation

serzhiio
Copy link

@serzhiio serzhiio commented Jun 1, 2020

Body::from_file() maybe is not working

Cargo.toml Outdated
@@ -39,6 +49,7 @@ url = "2.1.1"
serde_json = "1.0.51"
serde = { version = "1.0.106", features = ["derive"] }
serde_urlencoded = "0.6.1"
piper = "*"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

piper is deprecated

cookie-secure = ["cookie/secure"]

[dependencies.futures-io]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using futures and piper I would suggest using async-std with the default features, especially the runtime turned off. This way nothing changes in terms of code, but you are not forced to pull in the async-std runtime anymore, just the tooling like channels etc.

Copy link
Member

@dignifiedquire dignifiedquire Jun 3, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with async-rs/async-std#806 this

async-std = { version = "1.6", default-features = false, features = ["unstable"] }

should not pull in any runtime

@serzhiio
Copy link
Author

serzhiio commented Jun 3, 2020 via email

Copy link
Member

@yoshuawuyts yoshuawuyts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @serzhiio thanks for opening this PR. I've looked at this and agree with @dignifiedquire. Configuring async-std to not include the runtime indeed seems like a more sustainable solution.

@yoshuawuyts
Copy link
Member

It's been a month since the last activity on this PR, with a fair few changes requested. We may want to switch async-std for a few smaller dependencies (async-channel comes to mind), but we can probably do that through a different PR. Going to close this out for now.

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.

3 participants