Skip to content

Conflicting library names within an isolate should be allowed (VM) #9053

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
gbracha opened this issue Mar 11, 2013 · 4 comments
Closed

Conflicting library names within an isolate should be allowed (VM) #9053

gbracha opened this issue Mar 11, 2013 · 4 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant

Comments

@gbracha
Copy link
Contributor

gbracha commented Mar 11, 2013

Per the resolution of bug 5715, it is no longer a compile-time error to import two libraries of the same name in the same isolate.

@gbracha
Copy link
Contributor Author

gbracha commented Mar 11, 2013

Changed the title to: "Conflicting library names within an isolate should be allowed (VM)".

@iposva-google
Copy link
Contributor

Zach, please determine the current status and work with Matthias to fix this if necessary.


cc @mhausner.
Set owner to @zanderso.
Added Accepted label.

@zanderso
Copy link
Member

The Dart VM currently accepts this code without errors or warnings.

liba.dart:
  library mylib;
  // defines a function foo
  ...

libb.dart:
  library mylib;
  // defines a function bar
  ...

test.dart:
  import 'liba.dart';
  import 'libb.dart';
  // calls foo and bar
  ...

Do I understand correctly that this was the issue?

@iposva-google
Copy link
Contributor

Thanks!


Added AssumedStale label.

@gbracha gbracha added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant labels Apr 16, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Development

No branches or pull requests

3 participants