Preserve type variables in closure conversion.

pkg/kernel/test/closures_type_vars/suite.dart

Index: pkg/kernel/test/closures_type_vars/suite.dart
diff --git a/pkg/kernel/test/closures_type_vars/suite.dart b/pkg/kernel/test/closures_type_vars/suite.dart
new file mode 100644
index 0000000000000000000000000000000000000000..866bf2c40416dcfd18537b92172b7778f4f543f5
--- /dev/null
+++ b/pkg/kernel/test/closures_type_vars/suite.dart
@@ -0,0 +1,19 @@
+// Copyright (c) 2017, the Dart project authors. Please see the AUTHORS file
+// for details. All rights reserved. Use of this source code is governed by a
+// BSD-style license that can be found in the LICENSE.md file.
+
+library test.kernel.closures_type_vars.suite;
+
+import 'dart:async' show Future;
+import 'package:testing/testing.dart' show Chain, runMe;
+import '../closures/suite.dart' show ClosureConversionContext;
+
+Future<ClosureConversionContext> createContext(

[Dmitry Stefantsov, 2017/07/25 09:13:34]

Why do we need a new test suite?

[sjindel, 2017/07/25 13:11:48]

This one doesn't run the erasure transform. Not running it on the other tests
would cause a lot of expected file updates.

[Dmitry Stefantsov, 2017/07/26 09:12:09]

My understanding is that in future Erasure will be erased from [VmFastaTarget].

Do you think it is a good idea to turn [strongMode] on for all tests?  In this
case, we may reduce the number of test suites :)  It is ok to do that in a
separate CL.

[sjindel, 2017/07/26 10:37:45]

I'm indifferent.

+    Chain suite, Map<String, String> environment) async {
+  environment["updateExpectations"] =
+      const String.fromEnvironment("updateExpectations");
+  return ClosureConversionContext.create(
+      suite, environment, true /*strongMode*/);
+}
+
+main(List<String> arguments) => runMe(arguments, createContext, "testing.json");