Resolve type arguments to generic methods.

pkg/compiler/lib/src/resolution/members.dart

Index: pkg/compiler/lib/src/resolution/members.dart
diff --git a/pkg/compiler/lib/src/resolution/members.dart b/pkg/compiler/lib/src/resolution/members.dart
index f566e405dcc5eb6b5fa34bfa8aa3739bfb8f5867..abbf93f5d59d1e412a0092d9a45bf6f6e1ade961 100644
--- a/pkg/compiler/lib/src/resolution/members.dart
+++ b/pkg/compiler/lib/src/resolution/members.dart
@@ -3006,6 +3006,8 @@ class ResolverVisitor extends MappingVisitor<ResolutionResult> {
   }
 
   ResolutionResult visitSend(Send node) {
+    // Resolve type arguments to ensure that these are well-formed types.
+    visit(node.typeArgumentsNode);

[eernst, 2016/11/30 10:39:01]

I basically buy the argument that we can reject "meaningless" programs and
accept "meaningful ones that violate constraints".

I suspect that developers will be confused (they are not likely to see that
distinction spontaneously, and `dart2js` won't help them, it just emits warnings
about certain method invocation type arguments being non-types and accepts
malboundedness silently).

Anyway, I think almost all developers will get their messages from the analyzer,
so we don't really have to worry about all those wrong programs, because they
won't compile them before the analyzer is happy.

So we're good. ;-)

[Johnni Winther, 2016/11/30 11:51:03]

Acknowledged.

     if (node.isOperator) {
       // `a && b`, `a + b`, `-a`, or `a is T`.
       return handleOperatorSend(node);