Felix S.

First of all, the test suite is failing. I will not be merging anything without that fixed. Second, this may conflict with #98 when it is finally merged. And finally,...

There are two kinds of expressions which may evaluate to a value tuple: function calls and the vararg literal, `...`. There are also five places where discarding extra values matters,...

I think I will drop PhantomJS… and replace it with [duktape](https://github.com/svaarala/duktape). It may take some time to set it up under Travis CI, however, so I won't be doing it...

The more important issue is what to do with `spec`, however. It is still available from npm and still works, but I don't think it's wise to rely on an...

I upgraded some build dependencies and as of 626f3e4ee6882dd83b8a2b51a6e2c8ecc274840a I managed to shut up `npm audit` at least. That has to count for something. The issue is still unresolved, though.

I’ll think I’ll add a re-entrant API in 0.3.2, while leaving the current one in place, with semantics preserved. Not sure what I’ll do in 0.4. I may remove the...

Not rejecting yet, but I am definitely not going to merge this as-is. - I am split on whether I am willing to support a proprietary dialect in the first...

Given that identifiers are always added to the current scope, how about passing metadata identifying the scope to the `onCreateScope` callback instead? Whoever provides the callbacks can pluck out the...

To my knowledge, unless @oxyc is sitting in a cave and secretly crafting a solution, this isn't being worked on currently. As the cliché goes, patches are welcome. I think...

When parse errors are made recoverable, it seems it shouldn't be too hard to go the whole way and introduce warning lints as well, or at least a mechanism for...