Editor: missing values from enclosing activations #19577
Comments
|
Set owner to @devoncarew. |
|
Removed this from the Later milestone. |
|
Removed Oldschool-Milestone-Later label. |
|
I don't believe these variables are captured currently - it would take a change to the VM to accommodate this. Re-assigning to the VM team. Removed the owner. |
|
This comment was originally written by @mhausner This is the same issue as 20047. I added some background to that bug, so closing this as duplicate. The short story is: it's unlikely that we start capturing variables that are not used in inner functions (closures). That's a real runtime cost which is not justified. |
rmacnak-google
added
Type-Enhancement
area-vm
kevmoo
added
type-enhancement
When paused at the throw, I expect the display for the activation of the inner to display the receiver and the locals. E.g., Foo.inner() should display this, x, y, and z.
In less trivial examples the activations of inner and outer can be far apart on the stack--and may be separated by other activations of the same functions with different enclosing contexts or different receivers--making it difficult to find the values of variables in the context one is looking at.
class Foo extends Super {
foo() {
var x = 1;
outer() {
var y = 2;
inner() {
var z = 3;
throw "x";
}
inner();
}
outer();
}
}
The text was updated successfully, but these errors were encountered: