thephoenixofthevoid

@0x0aNL consider commenting out the whole if block (as shown above). Without throw it is just wasting CPU time anyway. Also note that in case of actual stackoverflow, you WILL...

It will become a problem once we have a truly async resolution. In meanwhile it's ok to simply catch stack overflow. The reason is that you have to do something...

In case of async resolution we will have to fibers as a call stack to track the dependencies between contexts. Because of that the depth of call stack won't ever...

According to https://exploringjs.com/es6/ch_generators.html there are: 1) Generator function 2) Generator object "When you call a generator function genFunc(), you get a generator object". We need to distinguish using generator function...

With given changes the performance of wildcard version doubled, but ordinary emitter's performance decreased. This is because I temporary removed many micro optimizations that made it hard to refactor the...

Yeah, I am interested in continuing, but It's important to discuss changes. The project is much depended upon, changes I have proposed so far are massive. Long story short: need...

```ts export function lookahead(parser: Parser) { return new Parser(function (context) { const a = parser.action(context) if (a.type !== ActionResultType.OK) { return a } return merge(a, context.ok(a.value)) }) } export function...