-
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
Operation tree contains no nodes for local functions #19902
Comments
Tagging @dotnet/analyzer-ioperation - I believe we should fix this for 15.3 |
To be clear on the example above, remove unused parameters analyzer will report both source and predicate as unused parameters. |
@jinujoseph, should we bring this to the meeting today? |
This is just a bug which needs to be fixed,and manish already knows what needs to be done here. @mavasani do you have any concern from design perspective ? |
I presume Fred meant discuss the new IOperation API that must be introduced in 15.later, correct? I will work on the workaround for 15.3 meanwhile. |
Ah sure , can you put the proposed API shape for discussion today |
I was assuming that you had an API shape. If not, it doesn't matter for now. |
I am assuming we want to expose the body and the local function symbol, so the API should be pretty trivial:
|
We probably want to share a common sub-type with ILambdaExpression though: http://source.roslyn.io/#Microsoft.CodeAnalysis/Operations/ILambdaExpression.cs,14 |
Fixed with #20177 |
Operation tree for BoundLocalFunctionStatement has no child nodes.
We seemed to have added an OperationKind.LocalFunctionStatement, but added no IOperation interface for it, causing us to miss this bug when we added IOperationWithChildren.
The text was updated successfully, but these errors were encountered: