Added InterfaceMirror.newInstance().

lib/mirrors/mirrors.dart

Index: lib/mirrors/mirrors.dart
===================================================================
--- lib/mirrors/mirrors.dart	(revision 10017)
+++ lib/mirrors/mirrors.dart	(working copy)
@@ -266,6 +266,15 @@
    * declarations in this library.
    */
   Map<String, VariableMirror> variables();
+
+  /**
+   * Invokes the named constructor and returns a mirror on the result.
+   *
+   * TODO(turnidge): Properly document.
+   */
+  Future<InstanceMirror> newInstance(String constructorName,

[rmacnak, 2012/07/30 16:33:45]

newInstance is somewhat misleading as a Dart constructor need not return a newly
allocated object. Perhaps invokeConstructor?

[Ivan Posva, 2012/07/30 17:03:28]

The same "confusion" can happen in non-mirrored Dart as well:
var x = new Foo();

The instance assigned to x could have been around for a very long time already.
I would leave the name as is so that it matches the language construct. With
invokeConstructor I personally would expect that I need to allocate the object
first before calling the constructor.

+                                List<Object> positionalArguments,
+                                [Map<String,Object> namedArguments]);
 }
 
 /**