Christopher Allen

> How about adding an optional falsely attribute to createAsyncFunction, making it `createAsyncFunction (asyncFunc, varArgs)`, setting `func.varArgs = varArgs`. An excellent suggestion. I do wonder if it might be preferable...

> Sorry, I'm a little confused on what I should be looking at in that link. Mainly, as an example, the addition of `FunctionResult.Block` to allow any `NativeFunction` (not just...

The limiting factor is not Acorn (though updating it might not be a bad idea anyway), but that JS Intrpreter itself only understands ES5.1. So being able to *parse* `for...

> I try to repackage with [email protected] just now. Just make sure you specify the appropriate options to Acorn so that it will parse ES5 only.

> Is it something you are considering doing? This is a question for @NeilFraser—but I suspect the answer is no, because this will eventually be part of the roadmap of...

> What is the name of the funded project? [Code City](http://github.com/google/CodeCity/). But do note: "will *eventually* be *part of the roadmap*"—in its present form Code City is actually a less-complete...

@bendavis78: It would be a considerable amount of work. ES6 is quite a bit larger language than ES5.1, and ES2020 is even more so. I don't think it necessarily requires...

I think that get a proper answer to your question you will need to be more specific about what you mean by "threads". JS-Interpreter is single-threaded (like any other normal...

Ah hah: this is actually a documentation bug! The error is here, in code that you have copied verbatim from [thread.html](https://github.com/NeilFraser/JS-Interpreter/blob/master/demos/thread.html) (paraphrased for clarity): ```JS // Create an interpreter whose...

I'm interested in improving error messages in JS Interpreter (or rather: in a heavily modified fork of it I maintain). If you have any insight into how other interpreters produce...