-
Notifications
You must be signed in to change notification settings - Fork 5
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
EXPERIMENTAL DO NOT MERGE: build: replace async-lock
with tokio
locks in core-crypto
#766
Draft
coriolinus
wants to merge
1
commit into
main
Choose a base branch
from
prgn/build/tokio-locks-experiment
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is experimental work, the purpose of which is to see how hard it would be to just swap out the lock implementations. If all had gone well, then it would have been worthwhile to make this change for the `map` and `try_map` that `tokio`'s lock guards have, which could have improved the ergonomics of some of our internal methods. Unfortunately, the difficulty was more than trivial. While it took only a few minutes of mechanical work to swap out the imports and uses, this causes a handful of tests to fail. So it's not really worth proceeding further with this experiment until we've actually prioritized it.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #766 +/- ##
=======================================
Coverage 72.05% 72.05%
=======================================
Files 106 106
Lines 19737 19737
=======================================
Hits 14222 14222
Misses 5515 5515
Continue to review full report in Codecov by Sentry.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is experimental work, the purpose of which is to see how hard it would be to just swap out the lock implementations. If all had gone well, then it would have been worthwhile to make this change for the
map
andtry_map
thattokio
's lock guards have, which could have improved the ergonomics of some of our internal methods.Unfortunately, the difficulty was more than trivial. While it took only a few minutes of mechanical work to swap out the imports and uses, this causes a handful of tests to fail. So it's not really worth proceeding further with this experiment until we've actually prioritized it.
What's new in this PR
PR Submission Checklist for internal contributors
SQPIT-764
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.