Fix #323 bug in SemanticModel.GetAwaitExpressionInfo when await expression used as an expression statement.#326
Merged
jaredpar merged 2 commits intodotnet:masterfrom Feb 9, 2015
Merged
Conversation
… expression used as an expression statement.
Member
Author
|
@AlekseyTs Could you please 👍 here? |
Member
|
LGTM |
1 similar comment
Contributor
|
LGTM |
jaredpar
added a commit
that referenced
this pull request
Feb 9, 2015
Fix #323 bug in SemanticModel.GetAwaitExpressionInfo when await expression used as an expression statement.
Member
Author
|
@jaredpar ouch, I was going to squish the commit history before merging. |
dibarbet
pushed a commit
to dibarbet/roslyn
that referenced
this pull request
Nov 21, 2025
Move variable definition script
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #323