-
Notifications
You must be signed in to change notification settings - Fork 142
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
remove async_std
support
#1402
Comments
related: issues: PRs: |
cc @Fi3 pinging you so you're aware does Demand heavily rely on anything |
no we use only tokio |
re-opening, as we still have some left-overs:
I'll send a follow-up PR soon |
It's ready on my fork... I will open the PR.. |
sorry only saw this now |
maintaining support for
async_std
in SRI substantially increases the engineering effortsmeanwhile, the SRI application layer is built with
tokio
, which is already quite challenging to maintaintherefore, we should drop the
async_std
support to make things simpler and cleaner, and most importantly: something that allows our limited engineering resources to sustainably achieve production readinessSRI application layer (
roles
,network_helpers_sv2
,integration_tests_sv2
) should only officially supporttokio
The text was updated successfully, but these errors were encountered: