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
eernstg opened this issue
Oct 10, 2017
· 1 comment
Labels
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).gardeningtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The following tests in sdk/tests/language_2 use e.toString() to get a string representation of a given run-time type (e has type Type), and compares the result to string literals:
As mentioned in issue #12605, no guarantees are given for the return value of toString, including the one on Type, and in particular the output looks very different for user-defined classes and for the class Map in $minified mode.
Only generic_closure_test avoids user-defined classes and Map, so it may work, but the others will inherently fail with $minified.
This issue exists to make sure this situation is known, and it may be used to track an update to the tests (if that's given priority). I haven't given the issue area-dart2js because this is a problem with the tests, not with dart2js.
The text was updated successfully, but these errors were encountered:
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).gardeningtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The following tests in
sdk/tests/language_2
usee.toString()
to get a string representation of a given run-time type (e
has typeType
), and compares the result to string literals:As mentioned in issue #12605, no guarantees are given for the return value of
toString
, including the one onType
, and in particular the output looks very different for user-defined classes and for the classMap
in$minified
mode.Only
generic_closure_test
avoids user-defined classes andMap
, so it may work, but the others will inherently fail with$minified
.This issue exists to make sure this situation is known, and it may be used to track an update to the tests (if that's given priority). I haven't given the issue
area-dart2js
because this is a problem with the tests, not with dart2js.The text was updated successfully, but these errors were encountered: