Rewrite how we handle synthesized constructors in the compiler. This was motivated by issue https:/…

sdk/lib/_internal/compiler/implementation/deferred_load.dart

Index: sdk/lib/_internal/compiler/implementation/deferred_load.dart
===================================================================
--- sdk/lib/_internal/compiler/implementation/deferred_load.dart	(revision 25107)
+++ sdk/lib/_internal/compiler/implementation/deferred_load.dart	(working copy)
@@ -240,6 +240,7 @@
         compiler.enqueuer.resolution.getCachedElements(element);
     if (elements == null) return new LinkedHashSet<Element>();
     Node node = element.parseNode(compiler);
+    if (node == null) return new LinkedHashSet<Element>();

[ahe, 2013/07/18 09:59:32]

Not sure about this. The synthetic element may contain an implicit dependency.

[ahe, 2013/07/18 14:32:56]

Never mind. Since we only track dependencies at the granularity of top-level
elements, the implicit dependency on the superclass' constructor is recorded on
line 150 and 169.

     var collector = new DependencyCollector(elements, compiler);
     node.accept(collector);
     collector.dependencies.addAll(elements.otherDependencies);