-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Fix simplify lambda expression with unrelated assignment in other method #71324
Fix simplify lambda expression with unrelated assignment in other method #71324
Conversation
var outermostBody = invokedExpression.AncestorsAndSelf().LastOrDefault( | ||
n => n is BlockSyntax or ArrowExpressionClauseSyntax or AnonymousFunctionExpressionSyntax or GlobalStatementSyntax); | ||
if (outermostBody is null or GlobalStatementSyntax) | ||
outermostBody = syntaxTree.GetRoot(cancellationToken); |
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.
the prior walk always hit the compilation unit. which meant that we were always checking everything (Even unrelated code). now we keep walking up, and only go to the compilation unit if we were in a global statement.
var outermostBody = invokedExpression.AncestorsAndSelf().Last( | ||
n => n is BlockSyntax or ArrowExpressionClauseSyntax or AnonymousFunctionExpressionSyntax or CompilationUnitSyntax); | ||
var outermostBody = invokedExpression.AncestorsAndSelf().LastOrDefault( | ||
n => n is BlockSyntax or ArrowExpressionClauseSyntax or AnonymousFunctionExpressionSyntax or GlobalStatementSyntax); |
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.
Do we need to consider field or property initializers here?
Fixes #71300