Skip to content

Restrict behavior of callable classes - analyzer implementation #32156

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
stereotype441 opened this issue Feb 14, 2018 · 2 comments
Closed

Restrict behavior of callable classes - analyzer implementation #32156

stereotype441 opened this issue Feb 14, 2018 · 2 comments
Assignees
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
Milestone

Comments

@stereotype441
Copy link
Member

This is the analyzer component of meta-bug #32152. See the meta-bug for details.

@jmesserly
Copy link

not quite ready to send out, but I'm working on this in https://dart-review.googlesource.com/c/sdk/+/45141

@stereotype441
Copy link
Member Author

Marking as P1 since it is the last checkbox on P1 bug #31638, which in turn is the last checkbox on P1 bug #31640.

@stereotype441 stereotype441 added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Mar 22, 2018
@bwilkerson bwilkerson added this to the Dart2 Beta 4 milestone Mar 29, 2018
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. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

3 participants