[Webkit-unassigned] [Bug 183267] Web Inspector: Typing Symbol.next() causes iterator advancement

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 2 14:49:40 PST 2018


--- Comment #4 from Daniel Bates <dbates at webkit.org> ---
(In reply to Joseph Pecoraro from comment #1)
> Just autocomplete greedily evaluating functions. We should not do this in
> cases where there could be side-effects but generally it is useful to
> evaluate a function if there are no side-effects.

This bug does not have as much to do with the general implementation strategy of autocomplete to greedily evaluating functions (*) as it does with the fact that this implementation throws away the result of the evaluation (**) such that it is not possible to ever see this result or operate on it.

(*) Though this strategy as it is currently implemented without saving and restoring program state or bookkeeping of intermediary results is problematic. How does Chrome DevTools accomplish autocompletion?

(**) Obviously we keep the type information of the result so as to provide autocompletion and suggestions.

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

More information about the webkit-unassigned mailing list