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.

Sign up for GitHub

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

Jump to bottom

dynamic result_type instead of type parameter #31

Open
gkappler opened this issue Aug 23, 2021 · 0 comments
Open

dynamic result_type instead of type parameter #31

gkappler opened this issue Aug 23, 2021 · 0 comments

Comments

@gkappler
Copy link
Owner

gkappler commented Aug 23, 2021 •
edited
Loading

issue #30 pointed to possibly

  • refactor result_type to dynamic computation (not at construction time),
  • retain the option to assert a result_type with a WrappedParser.

TextParse.AbstractToken{T} compatibility required representing result_type as a type parameter.
This could be taken out of CombinedParsers though retaining compatibility with AbstractToken with a struct.

Maybe that also is a better option for state_type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gkappler