You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to import a getter named x and setter named x= from different libraries produces inconsistent results in the VM. If the getter is imported first, and there is no import prefix, there is no problem. Otherwise, an attempt to use the getter results in the following runtime error: No top-level getter 'x' declared. (or, if the import prefix is p: No top-level getter 'p.x' declared.)
These errors are incorrect. There's nothing in the spec requiring a getter and its corresponding setter to be imported from the same library; the two entities have different names so they should not conflict with each other.
Dart2js and the analyzer also mishandle this situation, but not in the same way.
I will submit shared tests shortly demonstrating the bug.
The text was updated successfully, but these errors were encountered:
stereotype441
added
the
area-vm
Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
label
Jan 31, 2016
Attempting to import a getter named
x
and setter namedx=
from different libraries produces inconsistent results in the VM. If the getter is imported first, and there is no import prefix, there is no problem. Otherwise, an attempt to use the getter results in the following runtime error:No top-level getter 'x' declared.
(or, if the import prefix isp
:No top-level getter 'p.x' declared.
)These errors are incorrect. There's nothing in the spec requiring a getter and its corresponding setter to be imported from the same library; the two entities have different names so they should not conflict with each other.
Dart2js and the analyzer also mishandle this situation, but not in the same way.
I will submit shared tests shortly demonstrating the bug.
The text was updated successfully, but these errors were encountered: