jimblandy
commented
12 years ago I totally agree.
The pattern I hope to see played out is that we spin out a series of APIs in the spirit of Debugger: CallProfiler; ObjectProfiler; EventLoopDebugger; and so on. On May 20, 2012 12:31 PM, "David Bruant" < reply@reply.github.com> wrote:
Mark Miller's thesis contains a picture (page 107 of the document, Figure 14.2) of an E Vat which is somehow the equivalent of a JavaScript WebWorker. The context a webpage runs in is a vat. A vat is made of a queue of "pending messages" which is what in the JavaScript world is called the event loop. It would be great if it was possible to inspect, represent (and why not dynamically interact with) the event loop and the list of pending messages, very much like we currently can mess with the call stack.
Reply to this email directly or view it on GitHub: https://github.com/jimblandy/DebuggerDocs/issues/5
Mark Miller's thesis contains a picture (page 107 of the document, Figure 14.2) of an E Vat which is somehow the equivalent of a JavaScript WebWorker. The context a webpage runs in is a vat. A vat is made of a queue of "pending messages" which is what in the JavaScript world is called the event loop. It would be great if it was possible to inspect, represent (and why not dynamically interact with) the event loop and the list of pending messages, very much like we currently can mess with the call stack.