Skip to content
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

Difference in Operation tree shape between VB and C# for invocations to extension methods #23625

Open
mavasani opened this issue Dec 6, 2017 · 1 comment
Labels
Area-Analyzers Bug Feature - IOperation IOperation Need Design Review The end user experience design needs to be reviewed and approved. _Product-level triaged
Milestone

Comments

@mavasani
Copy link
Member

mavasani commented Dec 6, 2017

A C# invocation of the form a.ExtensionMethod() leads to Operation tree with operation for a being the first Argument for the invocation and null value for IInvocationOperation.Instance.

A VB invocation of the same form a.ExtensionMethod() leads to Operation tree with operation for a being IInvocationOperation.Instance and no arguments.

@mavasani
Copy link
Member Author

mavasani commented Dec 6, 2017

Tagging @dotnet/analyzer-ioperation

@jinujoseph jinujoseph added this to the Unknown milestone Jun 22, 2018
@jinujoseph jinujoseph added the Need Design Review The end user experience design needs to be reviewed and approved. label Jun 22, 2018
@sharwell sharwell added this to In Queue in IDE: Design review Jun 25, 2018
@jinujoseph jinujoseph removed this from In Queue in IDE: Design review Aug 14, 2018
@sharwell sharwell added this to In Queue in IDE: Design review via automation Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Analyzers Bug Feature - IOperation IOperation Need Design Review The end user experience design needs to be reviewed and approved. _Product-level triaged
Projects
Status: In Queue
IDE: Design review
  
In Queue
Development

No branches or pull requests

2 participants