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

Investigate better parse error reporting #33

Open
Slakah opened this issue Sep 19, 2018 · 0 comments
Open

Investigate better parse error reporting #33

Slakah opened this issue Sep 19, 2018 · 0 comments

Comments

@Slakah
Copy link
Owner

Slakah commented Sep 19, 2018

I suspect parse errors can be better represented. The examples I've seen in fastparse seem to suggest this, I suspect I've just configured the project incorrectly.
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
@Slakah