Sami Vaarala

Thanks, I'll check the results out. For Duktape testing the best test case set would be the ES5.1 subset; although some ES2015+ features are implemented, naturally most ES2015+ tests will...

The `make test262test` target runs the ES5 test suite: https://github.com/svaarala/duktape/blob/master/Makefile#L750-L757

Supporting multiline strings without interpolation would be very simple. Interpolation is a bit trickier because it creates a more complicated dependency between lexing and compilation (essentially, expressions need to be...

Hmm, the syntax is defined in parts (TemplateHead, TemplateMiddle, TemplateTail) so maybe if that approach was used it could be worked in a bit easier. The compiler would see a...

> Semantically, `foo ${bar} quux` should be exactly equivalent to "foo " + bar + " quux". I don't think that would be too difficult to parse? There's nothing conceptually...

@kphillisjr Because string coercion and concatenation is a common feature it should probably be supported directly. There's an internal call to do that reasonably efficiently: `duk_concat()`. To be clear, there's...

Destructuring and pattern matching for LHS is quite common in e.g. ML-inspired languages. I have fond memories of using Standard ML of New Jersey for protocol writing for example, because...

I guess it would be relatively straightforward to add some custom behavior to the basic operations so that when they operate on objects, they'd detect and invoke custom methods. For...

Like I said above I'm not very excited about adding operator overloading because it's not really Ecmascript then anymore. But if overloading support was added, I'd find it awkward if...

@JoshEngebretson Agree, breaking compliance is not an option. One could add operator overloading by introducing the overload methods as internal properties (later private symbols) which wouldn't affect compliance for any...