You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For diagnostics we really want textual representations of the states and productions, e.g. tables for:
ProdIdx --> text
1 --> "tok1 nonterm (line 506 ilpars.fsy)"
State --> text
301 -->
"nonterm1: . tok1 (rule at line 506 ilpars.fsy)
nonterm1: . tok1 nonterm (rule at line 507 ilpars.fsy)"
302 -->
"nonterm1: tok1 . (rule at line 506 ilpars.fsy)
nonterm1: tok1 . nonterm (rule at line 507 ilpars.fsy)"
etc.
This information should probably just always be emitted by default - the slight increase in size is of no great concern in modern situations
The text was updated successfully, but these errors were encountered:
The parsers we generate already have some tables for auto-generation of diagnostics
We should extend this to allow better diagnosis of error recovery situations.
Currently for a grammar like this:
The parse will generate states something like this:
etc and we emit tables that contain this kind of information:
State --> ProdIdx list ( 300 --> [1; 2], 301 --> [1,2], ....)
ProdIdx --> NonTerm (1 --> nonterm1, 2 --> nonterm1, ...)
For diagnostics we really want textual representations of the states and productions, e.g. tables for:
ProdIdx --> text
State --> text
etc.
This information should probably just always be emitted by default - the slight increase in size is of no great concern in modern situations
The text was updated successfully, but these errors were encountered: