Keep all type arguments in summaries - dynamic or not.

pkg/analyzer/lib/src/summary/idl.dart

Index: pkg/analyzer/lib/src/summary/idl.dart
diff --git a/pkg/analyzer/lib/src/summary/idl.dart b/pkg/analyzer/lib/src/summary/idl.dart
index 5d7174a8e67fc0c25c274d2a844b121bfb90a7b5..31c65655073dd4bc914c048ec78f8591f8669fa5 100644
--- a/pkg/analyzer/lib/src/summary/idl.dart
+++ b/pkg/analyzer/lib/src/summary/idl.dart
@@ -202,8 +202,9 @@ abstract class EntityRef extends base.SummaryClass {
 
   /**
    * If this is an instantiation of a generic type or generic executable, the
-   * type arguments used to instantiate it.  Trailing type arguments of type
-   * `dynamic` are omitted.
+   * type arguments used to instantiate it.  If AST is used to create the

[Paul Berry, 2016/05/06 18:11:38]

IMO, the documentation in this file should specify what happens with AST
summaries, and should not mention what happens with element-based summaries. 
Rationale: the behavior of element-based summaries is a bug caused by the fact
that the element model doesn't allow us to tell the difference between implicit
and explicit type arguments; that bug should be documented in the element-based
summary code (and tests), not here.

So personally I would just say "If this is an instantiation of a generic type or
generic executable, the type arguments used to instantiate it (if any)."

[scheglov, 2016/05/06 19:12:36]

Done.

+   * summary, and the AST does not specify any type arguments, this list is
+   * empty.  If element model is used, this list is not empty.
    */
   @Id(1)
   List<EntityRef> get typeArguments;