-
Notifications
You must be signed in to change notification settings - Fork 219
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
Replace async-std with equivalent tokio functionality #2801
Conversation
matrix-sdk-common and matrix-sdk-crypto were repeating things that would be inherited from the workspace dependency specification anyways.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2801 +/- ##
==========================================
+ Coverage 81.36% 81.70% +0.34%
==========================================
Files 204 204
Lines 21051 21052 +1
==========================================
+ Hits 17128 17201 +73
+ Misses 3923 3851 -72
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
d32dbb4
to
7ff5f45
Compare
7ff5f45
to
52ac8f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems plausible to me
52ac8f1
to
84f1a2a
Compare
I decided to take another look at our use of async-std, and AFAICT we are not actually requiring any
Condvar
-specific functionality (I think the only case where it does more than tokio'sNotify
is when a specific piece of code wants to queue up to be "next in line" to operate on the mutex after the wait condition is fulfilled).We also got a new use in an example, but that was even easier to remove.
Requesting rich's review in addition to one from the team because he added the use of
async-std
sCondvar
.