add tool to verify dependency information

README.md

Index: README.md
diff --git a/README.md b/README.md
index 37a41516e7e620d7b9328695c20fb8f7274d6300..ce4a82e5e017cdf6435960621c753f6df003c1d3 100644
--- a/README.md
+++ b/README.md
@@ -19,14 +19,14 @@ and size of your framework or app.
 This package focuses on gathering libraries and tools that summarize all of that
 information. Bear in mind that even with all these tools, it is not trivial to
 isolate code-size issues. We just hope that these tools make things a bit
-earier.
+easier.
 
 ## Status
 
 [![Build Status](https://travis-ci.org/dart-lang/dart2js_info.svg)](https://travis-ci.org/dart-lang/dart2js_info)
 
 Currently, most tools available here can be used to analyze code-size and
-attibution of code-size to different parts of your app. With time, we hope to
+attribution of code-size to different parts of your app. With time, we hope to
 add more data to the `.info.json` files, and include better tools to help
 understand the results of type inference.
 
@@ -38,7 +38,7 @@ of this package and update when needed.
 ## Info API
 
 [AllInfo][AllInfo] exposes a Dart representation of the `.info.json` files.
-You can parse the information using `AllInfo.parseFromJson`. For example:
+You can parse the information using `AllInfo.fromJson`. For example:
 
 ```dart
 import 'dart:convert';
@@ -49,8 +49,9 @@ import 'package:dart2js_info/info.dart';
 main(args) {
   var infoPath = args[0];
   var json = JSON.decode(new File(infoPath).readAsStringSync());
-  var info = AllInfo.parseFromJson(json);
+  var info = new AllInfo.fromJson(json);
   ...
+}
 ```
 
 ## Available tools
@@ -68,7 +69,7 @@ The following tools are a available today:
     or all libraries that match certain name pattern).
 
   * [`function_size_analysis`][function_analysis]: a tool that shows how much
-    code was attributed to each function. This tool also uses depedency
+    code was attributed to each function. This tool also uses dependency
     information to compute dominance and reachability data. This information can
     sometimes help determine how much savings could come if the function was not
     included in the program.
@@ -79,6 +80,10 @@ The following tools are a available today:
     `live_code_size_analysis` can correlate that with the `.info.json`, so you
     determine why code that is not used is being included in your app.
 
+  * [`verify_deps`][verify_deps]: a tool that verifies that all elements are
+    reachable from the program's entrypoint. If there are unreachable elements,
+    this indicates that the dependency information is incomplete.
+
 Next we describe in detail how to use each of these tools.
 
 ### Code deps tool
@@ -184,7 +189,7 @@ size attributed of all libraries, constants, and the program size.
 
 **Note**: eventually you should expect all numbers to add up to the program
 size. Currently dart2js's `--dump-info` is not complete, so numbers for
-bootstraping code and lazy static initializers are missing.
+bootstrapping code and lazy static initializers are missing.

[Siggi Cherem (dart-lang), 2015/10/14 23:37:02]

thanks for all the typo fixes!

[Harry Terkelsen, 2015/10/15 00:13:55]

no problem :)

 
 ### Function size analysis tool
 
@@ -251,12 +256,30 @@ dart2js_info_coverage_log_server main.dart.js
     `mail.dart.js.coverage.json`
 
   * Finally, run the live code analysis tool given it both the info and
-    converage json files:
+    coverage json files:
 
 ```bash
 dart2js_info_live_code_size_analysis main.dart.info.json main.dart.coverage.json
 ```
 
+### Verifying dependencies
+
+Coverage of dependency information may be incomplete. If there are elements that
+are live in the output that are unreachable through dependencies from the
+program's entrypoint, then we have incomplete dependency information. Note,
+however, that all elements may be reachable from the entrypoint even if there
+is missing dependency information. In order to verify that all elements are
+reachable from the app's entrypoint, simply run the tool as so:
+
+```bash
+dart2js_info_verify_deps foo.info.json
+```
+
+If all elements are reachable from the entrypoint, then the tool will not
+output anything and will return with exitcode 0. Otherwise, the tool will

[Siggi Cherem (dart-lang), 2015/10/14 23:37:02]

sometimes not seeing any results feels like a mystery. How about we print a
single line saying "everything appears reachable" or something similar?

[Harry Terkelsen, 2015/10/15 00:13:55]

Done.

+output the list of all functions that are not reachable from the entrypoint
+and return with exitcode 1.
+
 ## Code location, features and bugs
 
 This package is developed in [github][repo].  Please file feature requests and
@@ -269,4 +292,5 @@ bugs at the [issue tracker][tracker].
 [coverage]: https://github.com/dart-lang/dart2js_info/blob/master/bin/coverage_log_server.dart
 [live]: https://github.com/dart-lang/dart2js_info/blob/master/bin/live_code_size_analysis.dart
 [function_analysis]: https://github.com/dart-lang/dart2js_info/blob/master/bin/function_size_analysis.dart
+[verify_deps]: https://github.com/dart-lang/dart2js_info/blob/master/bin/verify_deps.dart
 [AllInfo]: http://dart-lang.github.io/dart2js_info/doc/api/dart2js_info.info/AllInfo-class.html