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.

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

Origin of type errors #22

Open
abooij opened this issue Oct 22, 2015 · 1 comment
Open

Origin of type errors #22

abooij opened this issue Oct 22, 2015 · 1 comment

Comments

@abooij
Copy link
Contributor

abooij commented Oct 22, 2015

The error message for type checking errors, while correct, is rather unhelpful in bigger proofs. It would be nice if it could at least state a line number where things go haywire.

It looks like this data is not exposed by bnfc, so we'd have to prepend position to every token. Or is there a less invasive solution?

@mortberg
Copy link
Owner

Yes, I think our error messages are pretty bad overall. Also, the REPL just crashes sometimes when you input something which it cannot parse. However our main priority at the moment is to document and check the correctness of the system, so we don't really have time to improve the interface at the moment... However, it would be very welcome if someone made a pull request improving these kind of things. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants