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
Parser vs TriviaParser vs PrecedenceParser. Maybe RuleParser / TriviaParser / PrattParser (comment)?
We renamed ebnf "expressions" to parser/scanner "definitions", but left a lot of expr, expression, and expressions variables and methods in the codebase (comment).
PrecedenceParser uses "operators" for the top-level operators, and their inner operator definition, which is confusing. Maybe use "expressions" and "expression.operator" instead?
The text was updated successfully, but these errors were encountered:
Cleanup of pre-release changes, to make it easier for onboarding.
- Replace the older notation of EBNF "expressions" in codegen with the
newer/consistent parser/scanner terminology.
- Rename `PrecedenceParser::Operators` to
`PrecedenceParser::Expressions` for accuracy, as each contain their own
operator.
Closes#373
Parser
vsTriviaParser
vsPrecedenceParser
. MaybeRuleParser
/TriviaParser
/PrattParser
(comment)?expr
,expression
, andexpressions
variables and methods in the codebase (comment).PrecedenceParser
uses "operators" for the top-level operators, and their inner operator definition, which is confusing. Maybe use "expressions" and "expression.operator" instead?The text was updated successfully, but these errors were encountered: