This repository was archived by the owner on Jan 12, 2024. It is now read-only.
removed sync over async in LazyAsync #238
Merged
Conversation
This file contains hidden or 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
bettinaheim
reviewed
Jun 7, 2020
Contributor
bettinaheim
left a comment
bettinaheim
left a comment
There was a problem hiding this comment.
Lgtm, @cesarzc for a second set of eyes.
george-moussa
requested review from
johnazariah
and removed request for
george-moussa
johnazariah
approved these changes
Jun 12, 2020
Member
johnazariah
left a comment
johnazariah
left a comment
There was a problem hiding this comment.
Yes, I agree this looks cleaner!
Thanks for this, @filipw!
AniketDalvi
pushed a commit
that referenced
this pull request
Jul 1, 2020
Co-authored-by: bettinaheim <34236215+bettinaheim@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Updated
LazyAsyncto not perform sync-over-async (no longer explicitly blocks).This is detrimental to performance and in places where there is synchronization context (e.g. xUnit tests or non-.NET Core apps) it can lead to deadlocks.
More about this in the great posts from S. Toub and S. Cleary