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
Right now only "forward" parsing is supported but some infrastructure exists for "backward" parsing.
Everything is the same except:
A B changes order
lookahead turns into lookbehind and vice-versa
cons lists become snoc lists
can probably avoid doing this, at a performance cost
can't use iterator API for a snoc list (since only "reverse" iteration exists)
GSS ranges would be input_start..rule_end instead of rule_start..input_end
If we use the same SPPF nodes (keeping e.g. cons lists), then we can reuse SPPF nodes between forward and backward parsing, but the GSS would still have to be separate.
N.B.: "LTR"/"RTL" would be convenient terms but as per rust-lang/rust#30459 they're incorrect.
The text was updated successfully, but these errors were encountered:
Right now only "forward" parsing is supported but some infrastructure exists for "backward" parsing.
Everything is the same except:
A B
changes orderinput_start..rule_end
instead ofrule_start..input_end
If we use the same SPPF nodes (keeping e.g. cons lists), then we can reuse SPPF nodes between forward and backward parsing, but the GSS would still have to be separate.
N.B.: "LTR"/"RTL" would be convenient terms but as per rust-lang/rust#30459 they're incorrect.
The text was updated successfully, but these errors were encountered: