Refactor related parameterized rule and inline rule - #536
Conversation
22d16d3 to
02eb9fa
Compare
06ed102 to
851bd18
Compare
|
Resolve conflicts |
…terized_rules for clarity
…ted methods for consistency
… to "Parameterized rule" for consistency
…rized rules" for consistency in README
…ameterized rule" for consistency
851bd18 to
c4f1dab
Compare
|
I will review this PR. |
|
I agree to use "parameterized" in code base, actually "parameterized" is used in menhir code base. |
@yui-knk Indeed it is. We have reverted the function name to remain “Parameterizing” in fb02d43 |
|
LGTM |
| grammar.parameterizing_rule_resolver.redefined_rules.each do |rule| | ||
| @logger.warn("parameterizing rule redefined: #{rule}") | ||
| grammar.parameterized_resolver.redefined_rules.each do |rule| | ||
| @logger.warn("parameterized rule redefined: #{rule}") |
There was a problem hiding this comment.
MEMO) I had a little difficulty here. Since this is a warning against “parameterized rules” rather than function names, I did not use Parameterizing. I don't have any strong opinions on this, so I will revert back if it feels different.
The following refactoring was performed