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

Error(u32) is not used currently #10

Closed
Geal opened this issue Feb 26, 2015 · 1 comment
Closed

Error(u32) is not used currently #10

Geal opened this issue Feb 26, 2015 · 1 comment

Comments

@Geal
Copy link
Collaborator

Geal commented Feb 26, 2015

An error code might not be the best way to represent that something went wrong. Returning an accumulation of sub parser errors could indicate what parsing path failed, instead of a global parsing error.
@Geal
Copy link
Collaborator Author

Geal commented May 6, 2015

This is done, at last.

@Geal Geal closed this as completed May 6, 2015
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
@Geal