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

Improve parser error experience #1

Open
theY4Kman opened this issue Nov 25, 2018 · 0 comments
Open

Improve parser error experience #1

theY4Kman opened this issue Nov 25, 2018 · 0 comments

Comments

@theY4Kman
Copy link
Contributor

Currently, when a Pattern expression fails to parse, only the line and column numbers are given to aid in resolving the issue.

It would be nice if the source Pattern expression were reproduced, with an arrow pointing to the location of the problem. It'd be even nicer if pretty terminal colours were used. Nicer still if a more semantically substantial message than "no viable alternative at input" were displayed.
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
@theY4Kman