Skip to content

Analyzer should remove support for ?id operator #10469

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

Closed
gbracha opened this issue May 6, 2013 · 14 comments
Closed

Analyzer should remove support for ?id operator #10469

gbracha opened this issue May 6, 2013 · 14 comments
Assignees
Labels
legacy-area-analyzer Use area-devexp instead.
Milestone

Comments

@gbracha
Copy link
Contributor

gbracha commented May 6, 2013

Per spec. 0.41, this construct has been dropped.

@gbracha
Copy link
Contributor Author

gbracha commented May 6, 2013

Se issue #10466

@bwilkerson
Copy link
Member

Set owner to @bwilkerson.
Added this to the M6 milestone.

@bwilkerson
Copy link
Member

Analyzer is now producing an error for this construct.

@bwilkerson
Copy link
Member

Issue #11565 has been merged into this issue.

@bwilkerson
Copy link
Member

Removed this from the M6 milestone.
Added this to the M7 milestone.

@jwren
Copy link
Member

jwren commented Sep 19, 2013

M7 -> M8


Removed this from the M7 milestone.
Added this to the M8 milestone.

@bwilkerson
Copy link
Member

Removed this from the M8 milestone.
Added this to the Later milestone.

@danrubel
Copy link

Needs to be fixed by 1.0


Removed this from the Later milestone.
Added this to the M8 milestone.

@gbracha
Copy link
Contributor Author

gbracha commented Oct 16, 2013

Yes, please! I've been asked to raise bugs of language compliance to a higher priority.


Removed Priority-Medium label.
Added Priority-High label.

@bwilkerson
Copy link
Member

The analyzer is fully specification compliant. The analyzer is still parsing and producing AST nodes for this operator, but it is producing the required errors. The only effect of it's behavior is that it recovers better if it finds code that still tries to use this operator. This issue is still open so that I don't forget that we might want to go back and do some code clean-up after 1.0.


Removed this from the M8 milestone.
Added this to the Later milestone.
Removed Priority-High label.
Added Priority-Medium label.

@gbracha
Copy link
Contributor Author

gbracha commented Oct 16, 2013

Ok, but I question whether in 1.0 we should be giving messages about constructs that are not in the language. I understand you are trying to be helpful when processing at older code by giving the deprecated message, but I think it needs to go before 1.0.

@bwilkerson
Copy link
Member

Removed the owner.
Removed this from the Later milestone.
Added this to the 1.4 milestone.

@jwren
Copy link
Member

jwren commented May 1, 2014

@jwren
Copy link
Member

jwren commented May 1, 2014

Set owner to @jwren.
Added Fixed label.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead.
Projects
None yet
Development

No branches or pull requests

4 participants