Add a `RefParser` in library? about dart-petitparser HOT 3 CLOSED

I don't like this style of describing grammars: It forces you to think about cycles in the grammar while writing the grammar. For every reference you have to decide if you want to use abc() or ref(abc). In either case the result is suboptimal: abc() will duplicate potentially large parts of the grammar and its construction, ref(abc) will recreate the complete grammar from that point on while parsing (which is horribly inefficient time and space wise). Also these hard coded assumptions about cycles makes reusability impossible and introduces possibly hard to detect bugs. Furthermore, I don't buy the argument about type-safety: The CompositeGrammar way is exactly as type-safe as your proposal, except that it only tells you about wrong references when instantiating the grammar. However, this is still before the actual grammar is executed. This analysis could potentially be part of dart_analyzer, when it becomes possible to add custom rules.

That said, I am perfectly fine making _parse a public method. I already started to make some classes public, for better reusability outside the library. Let me know if this would help you?

from dart-petitparser.

Yes, if I can create my RefParser in my own code, that will be great !

from dart-petitparser.

Renamed _parse to parseOn in c64e941.

from dart-petitparser.