Support class and typedef literals as expressions.

lib/compiler/implementation/tree/nodes.dart

Index: lib/compiler/implementation/tree/nodes.dart
diff --git a/lib/compiler/implementation/tree/nodes.dart b/lib/compiler/implementation/tree/nodes.dart
index d279076354351064a57fbd44e8030b453e374360..533002913ff9fb9abc85d04d7cb3014accd3b983 100644
--- a/lib/compiler/implementation/tree/nodes.dart
+++ b/lib/compiler/implementation/tree/nodes.dart
@@ -300,11 +300,11 @@ class Send extends Expression {
            receiver.asIdentifier().isSuper();
   }
   bool get isOperator => selector is Operator;
-  bool get isPropertyAccess => argumentsNode === null;
+  bool get isPropertyAccessOrTypeReference => argumentsNode === null;

[ahe, 2012/10/08 09:13:42]

I'm having a hard time seeing why this name is better than the original. To take
this approach to its logical conclusion, shouldn't it be:
isPropertyAccessOrMethodReferenceOrTypeReference?

In my mind, this is not an improvement.

Also, depending on your perspective, a type is a property on the current
library. This is a perspective that is very natural to me.

[ngeoffray, 2012/10/10 07:32:24]

I also prefer the original name.

[karlklose, 2012/10/23 10:33:52]

I reverted that change.

   bool get isFunctionObjectInvocation => selector === null;
   bool get isPrefix => argumentsNode is Prefix;
   bool get isPostfix => argumentsNode is Postfix;
-  bool get isCall => !isOperator && !isPropertyAccess;
+  bool get isCall => !isOperator && !isPropertyAccessOrTypeReference;
   bool get isIndex =>
       isOperator && selector.asOperator().source.stringValue === '[]';
   bool get isLogicalAnd =>