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

Jump to bottom

Closures in initializers don't always work #6422

Closed
DartBot opened this issue Oct 31, 2012 · 3 comments
Closed

Closures in initializers don't always work #6422

DartBot opened this issue Oct 31, 2012 · 3 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@DartBot
Copy link

DartBot commented Oct 31, 2012

This issue was originally filed by ngeoffray@google.com

See tests language/constructor6_test.dart and language/closure_in_initializer_test.dart
@iposva-google
Copy link
Contributor

Removed Priority-Medium label.
Added Priority-Unassigned label.

@sgjesse
Copy link
Contributor

sgjesse commented Aug 22, 2013

Failing test language/constructor5_test.dart seems to expose the same problem.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Aug 22, 2013
@iposva-google
Copy link
Contributor

Stale.

@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
Assignees
No one assigned
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @sgjesse @iposva-google @DartBot