Fuzzy Parsing Example

See:

• https://github.com/antlr/antlr4/blob/master/doc/wildcard.md#nongreedy-parser-subrules

This could probably be done using Token Categories to match against “all” kinds of tokens combined with an alternation which includes the one option we care about.

e.g:

      $.RULE("fuzzyConstantFinder", () => {
        $.OR([
          // We may need a GATE here, e.g using backtracking to ensure we never incorrectly enter
         // the constant alternative. 
          {ALT: () => $.SUBRULE($.constant)}, //
          {ALT: () => $.CONSUME(AnyToken)}, // AnyToken should be defined using Token Categories.
        ]);
      });

      $.RULE("constant", () => {
           $.CONSUME(Public);
           $.CONSUME(Static);
           $.CONSUME(Final);
           $.CONSUME(Int);
           $.CONSUME(Ident);
      });

[bd82]

I’ve started playing around with a similar scenario which required consuming any kind of tokens between a “–” and a semiColon.

Basically the CSS 3 custom property syntax:

• https://www.w3.org/TR/css-variables-1/#custom-property

You can inspect the current state of the example here:

• https://github.com/SAP/chevrotain/commit/4a7eb7923a065832c0363e354723af2a33bad0e1

[bd82]

Consider expanding the fuzzy parsing example to a scenario in which the fuzzy matching acts as a default fall back.

e.g: 3 Alternatives, and the 3rd one being the fuzzy one which could conflict with the first 2.