Skip to content

Analyzer should not treat static final variables as constant #3553

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
gbracha opened this issue Jun 12, 2012 · 4 comments
Closed

Analyzer should not treat static final variables as constant #3553

gbracha opened this issue Jun 12, 2012 · 4 comments
Assignees
@scheglov
Labels
legacy-area-analyzer Use area-devexp instead.
Milestone
M1

Comments

@gbracha
Copy link
Contributor

gbracha commented Jun 12, 2012

See issue #3549. This should be fixed only after the libraries have been converted to use const variables where needed. Per spec 10.1.
@scheglov
Copy link
Contributor

Added Waiting label.

@scheglov
Copy link
Contributor

Set owner to @scheglov.
Added Accepted label.

@scheglov
Copy link
Contributor

https://codereview.chromium.org/10907215

Added Started label.

@scheglov
Copy link
Contributor

https://code.google.com/p/dart/source/detail?r=12336

Added Fixed label.

@gbracha gbracha added Type-Defect legacy-area-analyzer Use area-devexp instead. labels Sep 13, 2012
@gbracha gbracha added this to the M1 milestone Sep 13, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@scheglov scheglov

Labels
legacy-area-analyzer Use area-devexp instead.
Projects
None yet
Milestone
M1
Development

No branches or pull requests
2 participants
@scheglov @gbracha