Limit GrammarAST::new() to only being pub(crate)
#586
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure if we want this change, Previously/historically
GrammarAST::new()has beenpub.However, there is nothing pub really takes a
GrammarASTas a parameter and returns aYaccGrammar. Another possible use would be if they were (at least)PartialEqorPartialOrd, but it doesn't derive anything but debug.Everything else is basically a self parameter.
My recent changes adding the unstable
grammar_ast()function toCTParserBuilderdon't actually change this,because that takes a
ASTWithValidityInfo, and there is no way to go from aGrammarASTto that.Anyways, it might be a good time to reevaluate whether we still want this
pubor not.