Skip to content

Ambiguous imported type names should not be compile-time errors #6659

Closed
@DartBot

Description

@DartBot

This issue was originally filed by [email protected]


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

Metadata

Metadata

Assignees

Labels

area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions