Results 99 comments of Dmitry Soshnikov

Thanks; yeah, for now I'll keep this issue opened for further investigations, however, initial investigations showed that it'll be not trivial to transpile this (see https://github.com/DmitrySoshnikov/regexp-tree/issues/66 for details).

Yeah, it depends on the runtime support from #3. We should build the runtime in this repo, and also in the generic Babel plugin @nicolo-ribaudo is working on in https://github.com/babel/babel/pull/7105.

Yeah, it's [in the README](https://github.com/DmitrySoshnikov/babel-plugin-transform-modern-regexp#useruntime-option). But we'll add the implementation to this plugin in parallel with the Babel plugin. A lightweight runtime [already exists](https://github.com/DmitrySoshnikov/regexp-tree/blob/master/src/compat-transpiler/runtime/index.js) in the `regexp-tree`, it just needs...

Yes, for named capturing groups we've been working on [plugin-transform-named-capturing-groups-regex](https://www.npmjs.com/package/@babel/plugin-transform-named-capturing-groups-regex) to make it standard Babel transform. For now you can apply that transform on top as a workaround, and we...

@mike-marcacci, yes, would be great to add this, and I agree, actual usage of the groups is a game changer. We can discuss any strategy here, those described above are...

Yeah, great idea; just recently I was thinking to add support for recursive descent (from LL(1) grammars), but the recursive ascent sounds event better. I also agree that it's better...

@namiwang, yeah, would be a good addition to have L-attribute grammars (where each non-terminal on the RHS can have its own handler, and depend on the symbols on the left...

@namiwang, are you using Rust plugin? Usually if a production doesn't have a handler, it can be omitted altogether. In Rust plugin specifically you also don't need to specify types...

Gotcha, thanks. Yeah, I'll take a look into it, and will appreciate a PR in case if you get to it earlier.

Yeah, confirm, thanks for catching this; though, it's a rare edge-case, and in fact is a "forwardreference". Need to fix though. Similarly, named groups (`\k` should be a "back/forward"reference): ```regex...