-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Add a .messages file for Menhir #10020
Comments
I am working on improving error messages. It is a research project, I cannot tell exactly when it will be ready, but the situation should be better in a few months from now. My solution is not directly based on |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Still open unless @let-def has changed something. |
I confirm that I am still working on that topic (though this is not my main project and needs a lot more work) |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Still an issue. @let-def any updates? |
I can provide an update from my (imperfect) understanding: @let-def has indeed managed to finish a first prototype of an improved approach to error messages (I would hazard the guess that the result is in the lrgrep repository). But currently there is no active work on upstreaming support for OCaml error messages. I hope that @let-def or people using his work will actually try to upstream something, but probably not before a few months. |
@let-def has been working on upstreaming lrgrep into merlin first, which is a slightly easier place to experiment with things. We're in the process of getting set up to try this prototype out inside Jane Street. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I think we can all agree that better syntax error messages would be nice.
The text was updated successfully, but these errors were encountered: