Files
sdk/tests/corelib
kmillikin@google.com 6ab3c55366 Fix an assertion failure in dart2js.
In the CPS translation we assert that a mutable variable added to the CPS
term belongs to the function currently being compiled, which is reasonable.
However, in the JS backend this didn't work as written.  The variable
element can report that it belongs to a Dart function, and the function
currently being compiled can be a synthesized .call method of a closure
class representing that Dart function.

The solution presented here is to plumb the mapping from Dart function to
closure class .call methods through to where the mutable variables are
created.  It might be better, but a lot more complicated, to make the
variable elements able to correctly report their owner after closure
conversion.

R=asgerf@google.com, karlklose@google.com
BUG=

Review URL: https://codereview.chromium.org//1084413003

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@45636 260f80e4-7a28-3924-810f-c04153c831b5
2015-05-08 08:58:00 +00:00
..
2015-01-29 12:14:08 +00:00
2015-03-25 07:01:46 +00:00
2013-11-01 17:02:27 +00:00
2013-11-01 17:02:27 +00:00
2013-11-01 17:02:27 +00:00
2013-12-13 12:10:23 +00:00
2013-10-24 08:44:32 +00:00
2014-06-26 11:49:11 +00:00