Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recursive vs. One-shot Parser to fix #3 #4

Closed
wants to merge 0 commits into from

Conversation

bhavyakukkar
Copy link
Contributor

implements a fix for #3

  • new switch parse_defs on struct Parser that is read in Parser.read_one and disables parsing new syntax definitions if false
  • made Parser public so that it can be used directly without relying on fn parse
  • made field Parser.reader public so that it can be used as it was being used for reporting location of failure in fn parse
  • new Parser constructors Parser::recursive and Parser::one_shot to construct Parsers that do and do not have the ability to parse new syntax definitions, respectively
  • made fn Parser.read_all public so that it can be used directly without relying on fn parse

@bhavyakukkar
Copy link
Contributor Author

sorry for the force-push (synced with new changes in main by mistake)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant