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
I don't see anything in the withClock documentation that indicates whether one form is preferred over the other. When I run this with dart this_test.dart, I get:
00:00 +0: inner withClock
00:00 +1: outer withClock
00:00 +1 -1: outer withClock [E]
Expected: same instance as <Instance of 'Clock'>
Actual: <Instance of 'Clock'>
More weirdness, part 1
If I reverse the tests, they pass when running it through dart.
More weirdness, part 2
The "outer withClock" test by itself fails with flutter test or with pub run test. Each test passes individually when run directly through dart.
I still don't understand how the "outer withClock" test ever works at all, but I care a lot less about that knowing that I shouldn't expect it to work.
Consider this code:
I don't see anything in the
withClock
documentation that indicates whether one form is preferred over the other. When I run this withdart this_test.dart
, I get:More weirdness, part 1
If I reverse the tests, they pass when running it through
dart
.More weirdness, part 2
The "outer withClock" test by itself fails with
flutter test
or withpub run test
. Each test passes individually when run directly throughdart
.Ultimately I'd like to do:
but all of this weirdness seems to prevent that.
(I'm using Dart 2.8.1 with clock 1.0.1.)
The text was updated successfully, but these errors were encountered: