pkg/matcher: refactor with unittest v0.12 work

test/operator_matchers_test.dart

Index: test/operator_matchers_test.dart
diff --git a/test/operator_matchers_test.dart b/test/operator_matchers_test.dart
index b92986ce66031d1e5ab272731e132c3e8f94d93f..7cf0d59126f2f1b241ce3815a76344678c207073 100644
--- a/test/operator_matchers_test.dart
+++ b/test/operator_matchers_test.dart
@@ -5,13 +5,12 @@
 library matcher.operator_matchers_test;
 
 import 'package:matcher/matcher.dart';
-import 'package:unittest/unittest.dart' show test, group;
+import 'package:unittest/unittest.dart'
+    show test, group, expect, throwsArgumentError;

[nweiz, 2015/02/17 23:17:42]

Don't use "show" unless we absolutely have to.

[kevmoo, 2015/02/18 00:33:40]

This is very explicit. Since unittest exports matcher, I want to be clear what
we're getting from the matcher package and what we're getting from unittest.

If I eleminate 'show', I could just remove the matcher import entirely and this
code still works

[nweiz, 2015/02/18 00:42:07]

There's no distinction between the test getting something "from matcher" or
"from unittest". It's the same member regardless.
I don't necessarily think this is a bad thing.

[kevmoo, 2015/02/18 00:49:50]

To put it another way: unittest could change what it exports at any time and it
shouldn't affect the code's ability to run. Let's agree to disagree. :-)

 
 import 'test_utils.dart';
 
 void main() {
-  initUtils();
-
   test('anyOf', () {
     // with a list
     shouldFail(