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

[IOperation] GetOperation returns a superset of IOperations for given syntax nodes #18064

Closed
5 tasks
333fred opened this issue Mar 22, 2017 · 1 comment
Closed
5 tasks

Comments

@333fred
Copy link
Member

333fred commented Mar 22, 2017

Uber-tracking issue for all instances of this. We seem to have a pattern of returning an IOperation that contains the expected operation for a given syntax node, rather than returning just the operation for that syntax node.

@jinujoseph jinujoseph modified the milestones: 15.3, 15.later Apr 18, 2017
@jinujoseph jinujoseph added the Concept-API This issue involves adding, removing, clarification, or modification of an API. label Apr 19, 2017
@jinujoseph jinujoseph removed the Concept-API This issue involves adding, removing, clarification, or modification of an API. label May 3, 2017
@jinujoseph
Copy link
Contributor

We dont' need the uber bug. All these are legitimate issues that just need to be fixed. Our design is that if you ask for a sub-syntax-node you should get the operation whose syntax points to that node. So all this existing behavior is definitely broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants