Futago-za Ryuu

Sorry, just trying to understand what you want here 😄 Basically you want the location data to reflect whats passed via the options rather then from the starting index used...

> in the preceding example the first chunk, would have the correct location info, the second chunk would be very incorrect. the string "te" would be prepended to the second...

Have decided to implement this before v1, but will need to think of a concrete direction to take based on the OP's request and my post above.

I've updated the roadmap for this (above) and will start work during #569

I'm not sure why there isn't a readme: - https://unpkg.com/[email protected]/ has a readme - https://unpkg.com/[email protected]/ has no readme - https://unpkg.com/[email protected]/ has a readme The NPM page won't be updated until...

The most related one I could find is #45 but the OP of that issue proposes a different syntax (similar to what you've implemented in your metagrammar @polkovnikov-ph), but I...

I'm leaning towards choosing one of the following for shorthands syntax: - `=> expr;` _(needs support for syntax)_ - `{ => expr }` _(usable now, but needs unwrapping)_ - `{...

@mikeaustin Yea, that's about right, but there's no way for it to know where to end this sequence then, so will consume evrything after `=>`

Actually, I have been thinking, these changes might just work: ```js CodeBlock "code block" = "=>" _ expession:CallExpression { return `return ${ expession };`; } / "{" @Code "}" /...

Hey @krzysztofpniak, this was actually fixed (see #452 for more details). You can test it using: - `npm i pegjs@dev` - https://pegjs.org/development/try The difference now seems to be when the...