-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Ambiguous imported type names should not be compile-time errors #6659
Comments
This comment was originally written by rodion...@unipro.ru the test was renamed to 1_Imports_A03_t31 |
This comment was originally written by @mhausner Changed the title to: "Ambiguous imported type names should not be compile-time errors". |
Removed Priority-Medium label. |
This comment was originally written by @mhausner Regis, could you please check whether this bug is still accurate? I think you may have fixed this already. tests/co19/src/Language/13_Libraries_and_Scripts/1_Imports_A03_t31.dart The test fails for an unrelated reason. It does not import the expect package. When I add the necessary import, I get: $ dart --checked tests/co19/src/Language/13_Libraries_and_Scripts/1_Imports_A03_t31.dart Set owner to @crelier. |
This issue was originally filed by alexe.kaigorodov@gmail.com
In "13.1 Imports", the specification (v.013) says:
If a name N is referenced by a library L and N is introduced into the top
level scope L by more than one import then:
• It is a static warning if N is used as a type annotation.
• In checked mode, it is a dynamic error if N is used as a type annotation
and referenced during a subtype test.
• Otherwise, it is a compile-time error.
However, even when the first condition is met, Dart VM still yields a compile error.
Affected co 19 test:
Language/13_Libraries_and_Scripts/1_Imports_A03_t28.dart
The text was updated successfully, but these errors were encountered: