Skip to content

analyzer: void arrow functions should allow any rhs type #28940

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
floitschG opened this issue Mar 1, 2017 · 3 comments
Closed

analyzer: void arrow functions should allow any rhs type #28940

floitschG opened this issue Mar 1, 2017 · 3 comments
Assignees
@eernstg
Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Milestone
1.24

Comments

@floitschG
Copy link
Contributor

This is the analyzer issue for #28939.
@floitschG floitschG added the legacy-area-analyzer Use area-devexp instead. label Mar 1, 2017
@floitschG floitschG added this to the 1.23 milestone Mar 1, 2017
@floitschG floitschG mentioned this issue Mar 1, 2017
Closed
4 tasks
@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 Mar 9, 2017
@mit-mit mit-mit modified the milestones: 1.24, 1.23 Mar 15, 2017
@mit-mit
Copy link
Member

mit-mit commented Mar 15, 2017

Punting to 1.24 per dart-leads discussion.

@floitschG floitschG assigned eernstg and unassigned floitschG May 9, 2017
eernstg added a commit that referenced this issue May 10, 2017
@eernstg
Allowing e of any type in void f(...) => e in the analyzer.
025b83f 
Addresses #28940.

[email protected]

Review-Url: https://codereview.chromium.org/2870063002 .
@eernstg
Copy link
Member

eernstg commented May 10, 2017

Addressed by this CL.

@eernstg
Copy link
Member

eernstg commented May 11, 2017

Landed in 6cb0966.

@eernstg eernstg closed this as completed May 11, 2017
@eernstg eernstg mentioned this issue May 18, 2017
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eernstg eernstg

Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
1.24
Development

No branches or pull requests
4 participants
@bwilkerson @floitschG @eernstg @mit-mit