Ben L. Titzer

Hi, an interesting point. It's not quite true that the Virgil parser stops parsing; it mostly starts breaking out of inner productions and loops, but might continue to parse the...

> The problem with such a test is that engines can legally fail it, due to (legal) implementation or resource limits. And most likely, such engines (will) exist, even when...

Yeah, agree that "environment" is a better name, since there isn't nesting or even embedding. I was also thinking the section would go best just before the code section.

@conrad-watt Yes, I think conceptually they are very limited nested modules. I didn't want to unduly incorporate the generality of nested modules in this discussion, but that would probably be...

@kmiller68 The choice of linear memory was only for simplicity and discussion. An additional instruction that takes a GC byte array would also be fine with me. As for the...

Ok, summarizing some above points for further discussion: 1. Should the interface accept GC arrays of bytes? 2. How to handle asynchronous compilation? @cfallin @kg and @yuri91 all mentioned this...

Also, for reference, Wizard implements a function-at-a-time compilation as a host API. The API produces a new function in the calling instance, similar to `func.new`. As a lower bound, for...

Interesting idea @cfallin ! `func.ready` could even be spec'd to have more than one return value, so that `0` = not ready, `1` = ready, `2` = validation error. Then...

Agree on the blocking semantics. Somehow the engine doing an asynchronous write to a table feels dangerous and error-prone. E.g. if/when there are shared tables, what if two different threads...

I wonder if there's enough use case diversity to consider making space for hints directly as an immediate. For example, if we reserve a zero byte for future flags, the...