cache pub list results

pkg/analyzer/lib/file_system/memory_file_system.dart

Index: pkg/analyzer/lib/file_system/memory_file_system.dart
diff --git a/pkg/analyzer/lib/file_system/memory_file_system.dart b/pkg/analyzer/lib/file_system/memory_file_system.dart
index b038f45eb92ab1863a5b45e62e64dd41ea49d581..4de46a34c4636a231438b8d95a174b45ce4bd203 100644
--- a/pkg/analyzer/lib/file_system/memory_file_system.dart
+++ b/pkg/analyzer/lib/file_system/memory_file_system.dart
@@ -47,6 +47,30 @@ class MemoryResourceProvider implements ResourceProvider {
   @override
   Context get pathContext => posix;
 
+  /**
+   * Simulate revoked file access

[scheglov, 2015/02/22 19:31:31]

This comment describes the method from the perspective of one its applications.
It would be easier to understand if we explicitly stated that it will return a
snapshot and clear everything.

[danrubel, 2015/02/24 02:29:45]

Good point. I reworked this into a deleteFolder method with an appropriate
description.

+   * and return an object that can be passed to [restore].
+   */
+  clear() {

[scheglov, 2015/02/22 19:31:31]

Could we have some type here and in "restore"?
Even if we don't have any methods in the interface, just an empty marker
interface would be nicer than "dynamic" IMHO.

[danrubel, 2015/02/24 02:29:45]

That makes sense. Instead it was decided that a restore point did not make
sense, so I moved the restore point functionality out of this class and into the
test itself.

+    var restorePoint = new _MemoryRestorePoint(this);
+    _pathToResource.clear();
+    _pathToContent.clear();
+    _pathToTimestamp.clear();
+    // TODO(danrubel) notify watchers
+    return restorePoint;
+  }
+
+  /**
+   * Simulate restored file access based upon some earlier call to [clear].
+   */
+  void restore(var restorePoint) {
+    _pathToResource.clear();
+    _pathToContent.clear();
+    _pathToTimestamp.clear();
+    (restorePoint as _MemoryRestorePoint).restore(this);
+    // TODO(danrubel) notify watchers
+  }
+
   void deleteFile(String path) {
     _checkFileAtPath(path);
     _pathToResource.remove(path);
@@ -149,6 +173,30 @@ class MemoryResourceProvider implements ResourceProvider {
 
 
 /**
+ * A restore point captures the [MemoryResourceProvider] state
+ * so that it can be restored at later point.
+ */
+class _MemoryRestorePoint {
+  final Map<String, _MemoryResource> _pathToResource =
+      new HashMap<String, _MemoryResource>();
+  final Map<String, String> _pathToContent = new HashMap<String, String>();
+  final Map<String, int> _pathToTimestamp = new HashMap<String, int>();
+
+  _MemoryRestorePoint(MemoryResourceProvider provider) {
+    _pathToResource.addAll(provider._pathToResource);
+    _pathToContent.addAll(provider._pathToContent);
+    _pathToTimestamp.addAll(provider._pathToTimestamp);
+  }
+
+  void restore(MemoryResourceProvider provider) {
+    provider._pathToResource.addAll(_pathToResource);
+    provider._pathToContent.addAll(_pathToContent);
+    provider._pathToTimestamp.addAll(_pathToTimestamp);
+  }
+}
+
+
+/**
  * An in-memory implementation of [File] which acts like a symbolic link to a
  * non-existent file.
  */