Implement tracing for function expressions and statements, and infer types of parameters of these c…

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

Index: sdk/lib/_internal/compiler/implementation/universe/universe.dart
===================================================================
--- sdk/lib/_internal/compiler/implementation/universe/universe.dart	(revision 31020)
+++ sdk/lib/_internal/compiler/implementation/universe/universe.dart	(working copy)
@@ -321,7 +321,6 @@
   }
 
   bool appliesUntyped(Element element, Compiler compiler) {
-    assert(sameNameHack(element, compiler));

[ngeoffray, 2013/12/10 17:11:02]

This is now also being called for closure calls, where the element name is the
closure name, and the selector name can be anything, depending on how the
closure is called.

[kasperl, 2013/12/11 07:35:35]

Should we get rid of all the sameNameHack stuff?

[ngeoffray, 2013/12/16 11:47:43]

I'll try, but some call sites do tricky things hard to work around.

     if (Elements.isUnresolved(element)) return false;
     if (isPrivateName(name) && library != element.getLibrary()) return false;
     if (element.isForeign(compiler)) return true;