Shahar Soel

> I will close this as I got a local solution that does the exact same thing just extends the CstParser Why? I have not looked into this yet but...

> but if you're philosophically against backtracking, I wasn't sure I should invest much time into it. I prefer to avoid backtracking where possible, but if there is an **easy**...

I wonder: 1. Could I remove built-in back-tracking support in Chevrotain? 2. Could back-tracking be implemented as an optional plugin (same as LL-star lookahead). Basically It was always recommended to...

## Backtracking as a Plugin details It seems many of the changes (at least in the PR) are either: 1. at the start of a method 2. at the end...

Hello @LaurensRietveld Could this be extended in a generic manner to improve the Chevrotain types? - https://github.com/Chevrotain/chevrotain/blob/a0a3856069c257c77dc3183efa0048a41ab8f88b/packages/types/api.d.ts#L409-L410

In theory it could be changed to a Map instead of a dictionary at some point. I am not sure its that important to expose it, particularly when it is...

- Could a simplified separate repo combined with gitpod / GH spaces link/config be easier to use for "playground" purposes? - What about life-cycle management issues between multiple repos?

Thanks @aral I wonder if **c8** would work on V8 processes inside electron. For example to obtain coverage for a VSCode extension during integration tests.

> @bd82 Haven’t tried it but I don’t see why not. Give it a shot and let us know? ;) @aral I will try to find time for this next...

Unfortunately I don't seem to find the time to investigate C8 + VSCode extensions coverage... But I found some info related to my original question here: - https://github.com/facebook/jest/issues/11188