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

Effective use of ParseFailed #6

Open
Iruyan-Zak opened this issue Jun 25, 2017 · 1 comment
Open

Effective use of ParseFailed #6

Iruyan-Zak opened this issue Jun 25, 2017 · 1 comment

Comments

@Iruyan-Zak
Copy link
Collaborator

Now, when parser1 <|> parser2 is failed to parse, the result becomes Left ParseFailed[reason1, reason2].
But if either of these consists of choice((<|>), choice), the result becomes a nest of ParseFailed [].
It doesn't seem better method.

Does anyone be coming up with better way?
(ParseFailed may be used for generating compilation errors. So I wish it be meaningful for it.)
@Roadagain
Copy link
Member

well... concat ?

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
2 participants
@Roadagain @Iruyan-Zak