add from option to run

lib/initialize.dart

Index: lib/initialize.dart
diff --git a/lib/initialize.dart b/lib/initialize.dart
index c5d07dd92d778945d129550b0c452e61b6cb226e..d93b4a785cd64a81360ae6505f8643b93d864e86 100644
--- a/lib/initialize.dart
+++ b/lib/initialize.dart
@@ -12,12 +12,16 @@ part 'src/init_method.dart';
 part 'src/initializer.dart';
 
 /// Top level function which crawls the dependency graph and runs initializers.
-/// If `typeFilter` and/or `customFilter` are supplied then only those types of
+/// If [typeFilter] and/or [customFilter] are supplied then only those types of
 /// annotations will be parsed. If both filters are supplied they are treated
 /// as an AND.
-Future run({List<Type> typeFilter, InitializerFilter customFilter}) {
+/// If [from] is supplied then initializers will be found starting from the
+/// library at the supplied uri. This option will throw once transformed since

[Siggi Cherem (dart-lang), 2015/03/23 20:25:55]

let's rephrase this last sentence a bit, to make it clear how this affects an
average user of the initialize package. One idea:

**Do not use this argument** directly in your code unless you are building a
framework that will use a transformer to remove this argument later. This
parameter is supported in Dartium, but [run] will throw if you use the argument
after building an application with `pub build`. 

[jakemac, 2015/03/23 20:58:03]

Done.

+/// that information is not available any more (all initializers are statically
+/// inlined at that point).
+Future run({List<Type> typeFilter, InitializerFilter customFilter, Uri from}) {
   return _runInitQueue(loader.loadInitializers(
-      typeFilter: typeFilter, customFilter: customFilter));
+      typeFilter: typeFilter, customFilter: customFilter, from: from));
 }
 
 Future _runInitQueue(Queue<Function> initializers) {