Support type variables as expressions.

sdk/lib/_internal/compiler/implementation/resolution/members.dart

Index: sdk/lib/_internal/compiler/implementation/resolution/members.dart
diff --git a/sdk/lib/_internal/compiler/implementation/resolution/members.dart b/sdk/lib/_internal/compiler/implementation/resolution/members.dart
index cb5811e80bbe66ab8f6b6e4a5f9e9484c7ee1dcd..37529867d106e828efb3d2d3b066b29b5cebd2e0 100644
--- a/sdk/lib/_internal/compiler/implementation/resolution/members.dart
+++ b/sdk/lib/_internal/compiler/implementation/resolution/members.dart
@@ -2198,6 +2198,11 @@ class ResolverVisitor extends CommonResolverVisitor<Element> {
               warnAndCreateErroneousElement(node.selector, field.name,
                                             MessageKind.CANNOT_RESOLVE_GETTER);
         }
+      } else if (target.isTypeVariable()) {
+        ClassElement cls = target.getEnclosingClass();
+        assert(enclosingElement.getEnclosingClass() == cls);
+        compiler.world.registerClassUsingVariableExpression(cls);

[ngeoffray, 2013/03/12 09:18:07]

As discussed, it'd be nice to not have to do this, and have all rti things being
handled in the backend.

[karlklose, 2013/03/12 09:35:22]

I'll move all RTI infrastructure from World to RuntimeTypeInformation in a
follow up CL.

+        compiler.backend.registerTypeVariableExpression(mapping);
       } else if (target.impliesType() && !sendIsMemberAccess) {
         compiler.backend.registerTypeLiteral(mapping);
       }