Add support for the new function-type syntax.

pkg/front_end/lib/src/fasta/parser/listener.dart

Index: pkg/front_end/lib/src/fasta/parser/listener.dart
diff --git a/pkg/front_end/lib/src/fasta/parser/listener.dart b/pkg/front_end/lib/src/fasta/parser/listener.dart
index 01d30edeffe24a2644c90eefa5f1623c944d4348..f8c0d69c20cf4ad4aaf46fee8b3531ea4acebefe 100644
--- a/pkg/front_end/lib/src/fasta/parser/listener.dart
+++ b/pkg/front_end/lib/src/fasta/parser/listener.dart
@@ -224,10 +224,10 @@ class Listener {
     logEvent("FunctionName");
   }
 
-  void beginFunctionTypeAlias(Token token) {}
+  void beginTypedef(Token token) {}

[ahe, 2017/02/14 12:43:02]

Why rename this?

[floitsch, 2017/02/14 13:56:17]

Because it's the end of a `typedef`, and we are considering allowing typedefs
for other types as well.

[ahe, 2017/02/15 11:50:17]

That's precisely why I'd like to keep calling this a function-type alias: I
assume there are other kinds of typedefs, and this event is about function-type
aliases.

 
-  void endFunctionTypeAlias(Token typedefKeyword, Token endToken) {
-    logEvent("FunctionTypeAlias");
+  void endTypedef(Token typedefKeyword, Token equals, Token endToken) {
+    logEvent("Typedef");
   }
 
   void beginMixinApplication(Token token) {}
@@ -504,7 +504,7 @@ class Listener {
 
   /// This event is added for convenience. Normally, one should use
   /// [endClassDeclaration], [endNamedMixinApplication], [endEnum],
-  /// [endFunctionTypeAlias], [endLibraryName], [endImport], [endExport],
+  /// [endTypedef], [endLibraryName], [endImport], [endExport],
   /// [endPart], [endPartOf], [endTopLevelFields], or [endTopLevelMethod].
   void endTopLevelDeclaration(Token token) {
     logEvent("TopLevelDeclaration");
@@ -554,6 +554,10 @@ class Listener {
     logEvent("Type");
   }
 
+  void handleNoName(Token token) {}
+
+  void endFunctionType(Token functionToken, Token endToken) {}

[ahe, 2017/02/14 12:43:02]

I can't find a matching beginFunctionType.

[floitsch, 2017/02/14 13:56:17]

There is none. The parser doesn't see when a function type starts. In other
words, it may start reading a type (say "int") before it realizes that a
"Function" is there. At that point it would be too late to call the
"beginFunctionType", since "int" is also part of the function type.

[ahe, 2017/02/15 11:50:17]

Could you document this here and on beginType? It's an exception to the overview
on lines 22-24.

[floitsch, 2017/02/16 16:30:15]

Changed to 'handleFunctionType' (same for "handleType").

Also added 'logEvent' to `handleNoName' and 'handleFunctionType'.

+
   void beginTypeArguments(Token token) {}
 
   void endTypeArguments(int count, Token beginToken, Token endToken) {