Skip to content

Analyzer handling of optional new and const. #30923

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.

Sign up for GitHub

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

Jump to bottom
Closed
lrhn opened this issue Sep 28, 2017 · 1 comment
Closed

Analyzer handling of optional new and const. #30923

lrhn opened this issue Sep 28, 2017 · 1 comment
Assignees
@bwilkerson
Labels
legacy-area-analyzer Use area-devexp instead. type-task A well-defined stand-alone task

Comments

@lrhn
Copy link
Member

lrhn commented Sep 28, 2017

This is the analyzer specific issue tracking #30921.

That analyzer will likely need to be aware of optional new and const.
The exact details depends on how the front-end chooses to represent the program.
@lrhn lrhn added the type-task A well-defined stand-alone task label Sep 28, 2017
@lrhn lrhn added this to the 2.0-beta1 milestone Sep 28, 2017
@lrhn lrhn mentioned this issue Sep 28, 2017
Open
7 tasks
@dgrove dgrove added the legacy-area-analyzer Use area-devexp instead. label Oct 5, 2017
@bwilkerson
Copy link
Member

I believe that this is now implemented, though I'm sure we'll find a few bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwilkerson bwilkerson

Labels
legacy-area-analyzer Use area-devexp instead. type-task A well-defined stand-alone task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dgrove @lrhn @bwilkerson