Francis McCabe

Actually, when listening to the discussion about the tracing instructions, I felt that they *should* be modeled as imports. So, I am also settling on option #1 - ruling them...

This reminds me, we have been toying with the idea of macros. Importing a macro sounds potentially like one way to model things like instrumentation and debugging features.

The ITT instructions are not transparent. I think that that is a large reason for some of the pushback here. Semantically, they seem to be very close to function calls.

Actually, I would argue that the cost of stack switch in #1360 is low. We have tried to get it to where it is comparable to the cost of a...

It is specifically NOT intended to affect JS programs. More precisely, trying to suspend a JS function will result in a trap. We have gone to some trouble to ensure...

@aardappel : > A function that has an answer inside of it needs to "inspectable", which means that, if it does register allocation at all, it needs to spill these...

@a-sully: As an outsider to this discussion, I need to take issue with: > Thank you for the feedback! At this point it's clear to me that the split sync/async...

return/return_throw is inspired by the way that Haskell functions return (by not actually constructing the value and signaling which constructor would have been used for the subsequent case analysis). The...

Small follow-on. I called out return_throw as a separate instruction from throw because throw requires a catch block to be statically determinable and return_throw leaves the function. On Thu, Jun...

The interlanguage case is dealt with by including error handling in the binding layer. That in turn implies that any exceptions that arise within an imported function (at least one...