Skip to content

Analyzer, support overriding fields in strong mode #28120

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
mit-mit opened this issue Dec 15, 2016 · 4 comments
Closed

Analyzer, support overriding fields in strong mode #28120

mit-mit opened this issue Dec 15, 2016 · 4 comments
Assignees
@jmesserly
Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Milestone
1.23

Comments

@mit-mit
Copy link
Member

mit-mit commented Dec 15, 2016 •
edited
Loading

This is the Analyzer part of meta-issue #28117.

Analyzer currently rejects an override with "Field declaration [field] cannot be overridden in SubClass.". This should be removed.
@mit-mit mit-mit added this to the 1.50 milestone Dec 15, 2016
@mit-mit mit-mit mentioned this issue Dec 15, 2016
Closed
5 tasks
@leafpetersen
Copy link
Member

This is blocked on resolution of finding an implementation strategy for DDC.

@jmesserly jmesserly added the status-blocked Blocked from making progress by another (referenced) issue label Dec 15, 2016
@jmesserly jmesserly mentioned this issue Dec 15, 2016
Closed
@bwilkerson bwilkerson added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) labels Jan 2, 2017
@kasperl kasperl modified the milestones: 1.23, 1.50 Feb 1, 2017
@kasperl kasperl mentioned this issue Feb 1, 2017
Closed
@mit-mit mit-mit added P1 A high priority bug; for example, a single project is unusable or has many test failures and removed P2 A bug or feature request we're likely to work on labels Feb 23, 2017
@bwilkerson
Copy link
Member

This is blocked on resolution of finding an implementation strategy for DDC.

Is there an issue tracking the need for this strategy? (More importantly, is someone working on developing the strategy?

@leafpetersen
Copy link
Member

This is blocked on #28809, and probably #28801 . Once those are resolved, we can flip the bit here.

@jmesserly
Copy link

https://codereview.chromium.org/2781443003/

@jmesserly jmesserly self-assigned this Mar 27, 2017
@jmesserly jmesserly removed the status-blocked Blocked from making progress by another (referenced) issue label Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmesserly jmesserly

Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
1.23
Development

No branches or pull requests
5 participants
@jmesserly @kasperl @bwilkerson @leafpetersen @mit-mit