[Webkit-unassigned] [Bug 152682] Web Inspector: Show upcoming values of non-native iterators

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=152682

--- Comment #5 from Joseph Pecoraro <joepeck at webkit.org> ---
> If they use iterators, why are they going to have any less trouble
> duplicating the iterator state than we are?

Our native iterators have a wrapper and an internal object. When we peek, we create a new wrapper, with the same data as the original wrapper, advance the new wrapper, then drop it on the floor. See JSMapIterator::clone, JSSetIterator::clone, etc.

I don't think we can make the same assumptions about any user script's object. And I'm not sure we can call execute _anything_ on the user object in a way that will guarantee no side-effects, as anything can be a getter.

The cop-out, which is what I'm suggesting, is a public function with a contract of "don't do side-effects, if you do it is your fault". The inspector can then call these. Problem is it requires libraries to author those functions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160105/af685aae/attachment-0001.html>