First step of support for parsing and ignoring generic methods.

pkg/compiler/lib/src/serialization/modelz.dart

Index: pkg/compiler/lib/src/serialization/modelz.dart
diff --git a/pkg/compiler/lib/src/serialization/modelz.dart b/pkg/compiler/lib/src/serialization/modelz.dart
index 07cf4e6e7b537419dd8f3804ad6a8b7370e73232..c8421810b38ed273ce5211efebba26c2879c3ea0 100644
--- a/pkg/compiler/lib/src/serialization/modelz.dart
+++ b/pkg/compiler/lib/src/serialization/modelz.dart
@@ -16,6 +16,7 @@ import '../compiler.dart'
     show Compiler;
 import '../constants/constructors.dart';
 import '../constants/expressions.dart';
+import '../core_types.dart';
 import '../dart_types.dart';
 import '../elements/elements.dart';
 import '../elements/modelx.dart' show
@@ -853,7 +854,7 @@ class ClassElementZ extends DeserializedElementZ
   bool get hasLocalScopeMembers => _unsupported('hasLocalScopeMembers');
 
   @override
-  bool implementsFunction(Compiler compiler) {
+  bool implementsFunction(CoreClasses coreClasses) {

[floitsch, 2016/02/22 12:45:20]

How is this change related to generic methods?

[eernst, 2016/02/22 18:02:51]

It is unrelated. The IDE complained about the type of this overriding method
declaration. The argument is unused here, and there is no obvious reason why the
argument type should differ from the inherited one. So I fixed it, considering
it to be a typo, in order to make the IDE happy (and, presumably, avoid a
potential checked-mode error that makes no sense anyway).

Should it be a separate CL?

[floitsch, 2016/02/22 18:40:27]

https://codereview.chromium.org/1723653002

[eernst, 2016/02/23 12:40:45]

OK, reverted it here.

     return _unsupported('implementsFunction');
   }