-
Notifications
You must be signed in to change notification settings - Fork 53
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
Research migrating to new async runtime (async-std -> tokio) #87
Comments
@a-moreira @Davidson-Souza , I was looking into the migration, few queries on this-
|
|
@lordshashank I started this effort here https://github.com/Davidson-Souza/Floresta/pull/110 but had to back away due to some personal reasons. Maybe that helps. |
This issue was proposed as a Summer of Bitcoin assignment right ? Can someone add the summer-of-bitcoin label ? |
@jaoleal I'm not aware of that, are you @Davidson-Souza? |
I can create the issue and tag both of you @a-moreira and @Davidson-Souza if you all prefer this way, since the tittle for this one is about research only... If so, I do appreciate some time so i can get more information about the work to be done, the affected modules, final objective, info source and etc... |
@jaoleal cool! It's ok for me. |
Hi @jaoleal. Yes, this project is one of my SoB's project ideas. I agree with @a-moreira, we know we want to do this, we just need to actually do. |
Done in #172 |
async-std
is not well maintained anymore, andtokio
seems to be the de-facto choice for an async runtime in Rust:https://corrode.dev/blog/async/
The text was updated successfully, but these errors were encountered: