Skip to content
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

dart2dart generates invalid typedef usage #11468

Closed
johnniwinther opened this issue Jun 24, 2013 · 3 comments
Closed

dart2dart generates invalid typedef usage #11468

johnniwinther opened this issue Jun 24, 2013 · 3 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue

Comments

@johnniwinther
Copy link
Member

In the face of function subtyping dart2dart generates invalid typedef usage:

language/dynamic_test
language/function_subtype_bound_closure0_test
language/function_subtype_bound_closure1_test
language/function_subtype_bound_closure2_test
language/function_subtype_bound_closure5_test
language/function_subtype_bound_closure6_test
language/function_subtype_bound_closure7_test
language/function_subtype_cast0_test
language/function_subtype_cast1_test
language/function_subtype_cast2_test
language/function_subtype_cast3_test
language/function_subtype_factory0_test
language/function_subtype_local1_test
language/function_subtype_local5_test
language/function_subtype_not0_test
language/function_subtype_not1_test
language/function_subtype_not2_test
language/function_subtype_not3_test
language/function_subtype_top_level1_test
language/function_type_alias2_test
language/function_type_alias3_test
language/function_type_alias4_test
language/function_type_alias6_test
language/function_type_alias_test
language/method_override_test

@DartBot
Copy link

DartBot commented Jun 24, 2013

This comment was originally written by antonm@google.com


John, may you, please, provide more details?

@johnniwinther
Copy link
Member Author

Its seem to work now. I'll close this bug if stays like that on the buildbot.

@johnniwinther
Copy link
Member Author

No. Bad luck. The bug is still there. I'm investigating.

@sethladd sethladd added the closed-not-planned Closed as we don't intend to take action on the reported issue label Jul 10, 2015
@kevmoo kevmoo removed the triaged label Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

4 participants