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

don't have sepBy0 and sepBy1 do complicated processing to their values #42

Closed
mattfenwick opened this issue Oct 2, 2016 · 3 comments
Closed

Comments

@mattfenwick
Copy link
Owner

mattfenwick commented Oct 2, 2016

Just return something like:

{'first': ..., 'pairs': [[..., ...], ...]}

Perhaps wrapped in a datatype that knows how to return all the values while ignoring the separators.

@mattfenwick
Copy link
Owner Author

This will simplify the operators combinators, as they won't have to deal with that funky datatype anymore.

@mattfenwick
Copy link
Owner Author

Done.

@mattfenwick
Copy link
Owner Author

This could maybe be taken even further, and have sepByN build the tree, as well.
They'd have to decide whether to left- or right-associate it, though.

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

No branches or pull requests

1 participant