Skip to content

dart2js: find main in exported names of main library #14762

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
kasperl opened this issue Nov 4, 2013 · 3 comments
Closed

dart2js: find main in exported names of main library #14762

kasperl opened this issue Nov 4, 2013 · 3 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures web-dart2js
Milestone

Comments

@kasperl
Copy link

kasperl commented Nov 4, 2013

The spec has changed. We need to look for main in the exported names of the main library -- not in the library itself. See issue #14541.

@kasperl
Copy link
Author

kasperl commented Nov 4, 2013

Fixed in r29809.


Added Fixed label.

@kasperl
Copy link
Author

kasperl commented Nov 4, 2013

Reverted due to a few test failures. Re-opening.


Set owner to @kasperl.
Added this to the M8 milestone.
Removed Priority-Unassigned label.
Added Priority-High, Started labels.

@kasperl
Copy link
Author

kasperl commented Nov 4, 2013

Fixed (again) in r29812.


Added Fixed label.

@kasperl kasperl added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures web-dart2js labels Nov 4, 2013
@kasperl kasperl self-assigned this Nov 4, 2013
@kasperl kasperl added this to the M8 milestone Nov 4, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures web-dart2js
Projects
None yet
Development

No branches or pull requests

1 participant