Skip to content

Constructors must not conflict with members: VM #3990

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
gbracha opened this issue Jul 4, 2012 · 3 comments
Closed

Constructors must not conflict with members: VM #3990

gbracha opened this issue Jul 4, 2012 · 3 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Milestone
M1

Comments

@gbracha
Copy link
Contributor

gbracha commented Jul 4, 2012

See issue #3040
@DartBot
Copy link

DartBot commented Sep 5, 2012

This comment was originally written by @mhausner

We have a few problems of constructor name clashes in the library and in dart2js.

Review will be out shortly.

Set owner to @mhausner.
Added Started label.

@DartBot
Copy link

DartBot commented Sep 6, 2012

This comment was originally written by @mhausner

Fixed at r11972. Check is guarded by runtime flag. Will remove runtime flag soon and enable check by default.

@DartBot
Copy link

DartBot commented Sep 6, 2012

This comment was originally written by @mhausner

Added Fixed label.

@gbracha gbracha added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. labels Sep 6, 2012
@gbracha gbracha added this to the M1 milestone Sep 6, 2012
This issue was closed.
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, and the AOT and JIT backends.
Projects
None yet
Milestone
M1
Development

No branches or pull requests
2 participants
@gbracha @DartBot