Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAre the changes from #637 LR(1) compatible? #776
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jmdyck
Jan 23, 2017
Collaborator
(I tried to generate an LR automaton, but couldn't figure out how to incorporate lookahead-restrictions into the algorithm.)
|
(I tried to generate an LR automaton, but couldn't figure out how to incorporate lookahead-restrictions into the algorithm.) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jmdyck
Jan 23, 2017
Collaborator
Yeah, it seems to me that after seeing export { IdentifierName, the parser has a couple of reduce actions available (reduce to Identifier or to ExportSpecifier[~Local]), but the only basis for deciding between them is the presence or absence of a FromClause, which is arbitrarily far away.
|
Yeah, it seems to me that after seeing |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Thanks for confirming @jmdyck! |
anba commentedJan 23, 2017
Has anyone checked if the grammar is still LR(1) with the changes from #637? When I use the following toy grammar to model the modifications from #637, I get shift/reduce and reduce/reduce conflicts.