Add a task for computing all constant values in a compilation unit.

pkg/analyzer/lib/task/dart.dart

Index: pkg/analyzer/lib/task/dart.dart
diff --git a/pkg/analyzer/lib/task/dart.dart b/pkg/analyzer/lib/task/dart.dart
index c8325e1c6ffcf42fe1497ca5ff58f826a0b4d121..0a3915b7e63fe345af63075008da03ce53a4adcd 100644
--- a/pkg/analyzer/lib/task/dart.dart
+++ b/pkg/analyzer/lib/task/dart.dart
@@ -14,6 +14,16 @@ import 'package:analyzer/src/task/dart.dart';
 import 'package:analyzer/task/model.dart';
 
 /**
+ * The resolved [CompilationUnit] associated with a compilation unit, with
+ * constants resolved.
+ *
+ * The result is only available for [LibrarySpecificUnit]s.
+ */
+final ResultDescriptor<CompilationUnit> CONSTANT_RESOLVED_UNIT =
+    new ResultDescriptor<CompilationUnit>('CONSTANT_RESOLVED_UNIT', null,
+        cachingPolicy: AST_CACHING_POLICY);
+
+/**
  * The analysis errors associated with a [Source] representing a compilation
  * unit.
  */
@@ -104,7 +114,8 @@ final ResultDescriptor<CompilationUnit> PARSED_UNIT =
         cachingPolicy: AST_CACHING_POLICY);
 
 /**
- * The resolved [CompilationUnit] associated with a compilation unit.
+ * The resolved [CompilationUnit] associated with a compilation unit, with
+ * constants not yet resolved.

[Brian Wilkerson, 2015/05/11 20:48:45]

I have to wonder how many clients want an AST in which constants have not yet
been resolved.

It might be less confusing if RESOLVED_UNIT were renamed to RESOLVED_UNIT5,
moved to the internal library, and CONSTANT_RESOLVED_UNIT were renamed to
RESOLVED_UNIT.

[Paul Berry, 2015/05/11 22:07:39]

Good point.  I will do this in a follow-up CL.

  *
  * The result is only available for [LibrarySpecificUnit]s.
  */