Skip to content

Better Parser Errors #12

@profbrandon

Description

@profbrandon

Right now the errors generated by the parser suck. Primarily, I believe this is because it only ever carries one error. It can keep multiple values in 'expected', but it doesn't alert the user as to what kind of parser failed. Moreover, it doesn't display the position that the error in the input occurred at.

In addition, it would be good if there was a pretty-printing function for parse errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementImprove a preexisting feature

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions