Sami Vaarala

@andoma Thanks, looks interesting! It should be possible to use VMIR for loosely coupling a WebAssembly executor to Duktape, as long as the WebAssembly Javascript transition works well enough.

All the stuff is in the main repo: - Some support code etc: https://github.com/svaarala/duktape/tree/master/dukweb - Build target: https://github.com/svaarala/duktape/blob/master/Makefile#L583-L587 Let me know how it goes, would be nice to know how...

@mikeptweet Awesome, I'll add that to the Makefile too :)

ES2015+ is certainly a goal, but some of the features will require a rewrite of the parser/compiler. For other features it's a more incremental process. For example, right now I'm...

I've used rollup and webpack, both seem to work OK.

At present the best approach is using a Proxy object. A Proxy can capture various operations (like [[Get]], [[Set]], [[DefineOwnProperty]] etc) and handle them in trap functions. It would be...

Proxy target must be an object, but it could be an object coerced pointer, Duktape.Pointer: ``` duk> new Proxy(new Duktape.Pointer('foo'), {}) = {} ``` The underlying value of a Duktape.Pointer...

That format ending with `%03dZ` is trying to format a 3-digit integer, followed by a literal `Z`. I don't know why it would be interpreted as a Z format string...

The values are range checked before the call, but the compiler probably doesn't carry that range information far enough. It would need to carry that information through the public API,...

I don't see how the compiler could be (reliably) made aware of the actual ranges of the values, so the solution would be either to suppress the warning (the buffer...