cleaning up the earley parsing #173
Merged
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.
predict_is_starting()to_predictbecause i find the former unintuitive_predict()return aTraversalIdinstead of&Traversalbecause most users were just taking the ID of the latter_predict()can now takeself, and it's wrapper funcs (predict_starting&predict) no longer have duplicated destructuring codematch_term()has also been made to return an ID for the same reason, which also had a similar loosening effect on the lifetimes and allowed me to remove that inner function workaroundearley(), making it a tad less verbose...and that's about it for now