This event may be reported during SLL prediction in cases where the conflicting SLL configuration set provides sufficient information to determine that the SLL conflict is truly an ambiguity. For example, if none of the ATN configurations in the conflicting SLL configuration set have traversed a global follow transition (i.e. {@link ATNConfig#reachesIntoOuterContext} is 0 for all configurations), thenthe result of SLL prediction for that input is known to be equivalent to the result of LL prediction for that input.
In some cases, the minimum represented alternative in the conflicting LL configuration set is not equal to the minimum represented alternative in the conflicting SLL configuration set. Grammars and inputs which result in this scenario are unable to use {@link PredictionMode#SLL}, which in turn means they cannot use the two-stage parsing strategy to improve parsing performance for that input.
@see ParserATNSimulator#reportAmbiguity @see ANTLRErrorListener#reportAmbiguity @since 4.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|