Will a PR for adding Parser.prototype.reportCurrentStatus() be acceptable?

[Henddher]

Hello 👋

While experimenting and debugging grammar, I often rely on Parser.prototype.reportErrorCommon(...) to "dump" the state of the parser.

> parser.reportErrorCommon("", "")
'
Unexpected . Instead, I was expecting to see one of the following:

A character matching /[^:]/ based on:
    plaintext$ebnf$1 →  ● /[^:]/
    plaintext →  ● plaintext$ebnf$1
    line →  ● plaintext
A ":" based on:
    colons$string$1 →  ● ":" ":"
    colons →  ● colons$string$1 colons$ebnf$1
    markup_line →  ● colons markup_def
    line →  ● markup_line
'

A PR adding Parser.prototype.reportCurrentStatus() would leverage a minor refactoring in reportErrorCommon.

Would that be acceptable?

[kach]

Sure, go ahead.