Use annotations on confuse() functions

tests/language/const_map2_test.dart

Index: tests/language/const_map2_test.dart
diff --git a/tests/language/const_map2_test.dart b/tests/language/const_map2_test.dart
index 6b599f70d1585a34903a5c6bf1f136c9197123f4..d32ca5b13ccbc0debbc3b5a678ce4b27f89a76bf 100644
--- a/tests/language/const_map2_test.dart
+++ b/tests/language/const_map2_test.dart
@@ -14,10 +14,8 @@ class B implements A {
   operator ==(o) => true;  /// 00: compile-time error
 }
 
-confuse(x) {
-  if (new DateTime.now() == 42) return confuse(2);
-  return x;
-}
+@NoInline() @AssumeDynamic()

[floitsch, 2015/12/09 20:40:14]

I would put them on separate lines, but I really don't mind if they stay the way
they are.

Since we seem to combine @NoInline() and @AssumeDynamic() a lot, it might be
worthwhile adding a new annotation to the test-package (providing both).

+confuse(x) => x;
 
 main() {
   // It is a compile-time error if the key type overrides operator ==.