Skip to content

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

Closed
DemiMarie opened this issue Nov 12, 2020 · 8 comments
Closed

Add a .messages file for Menhir #10020

DemiMarie opened this issue Nov 12, 2020 · 8 comments

Comments

@DemiMarie
Copy link
Contributor

I think we can all agree that better syntax error messages would be nice.

@let-def
Copy link
Contributor

let-def commented Nov 12, 2020

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 .messages but could be seen as a generalization.

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Nov 15, 2021
@DemiMarie
Copy link
Contributor Author

Still open unless @let-def has changed something.

@github-actions github-actions bot removed the Stale label Nov 17, 2021
@let-def
Copy link
Contributor

let-def commented Nov 22, 2021

I confirm that I am still working on that topic (though this is not my main project and needs a lot more work)

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Nov 25, 2022
@DemiMarie
Copy link
Contributor Author

Still an issue. @let-def any updates?

@gasche
Copy link
Member

gasche commented Nov 25, 2022

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.

@gasche gasche removed the Stale label Nov 25, 2022
@lpw25
Copy link
Contributor

lpw25 commented Nov 25, 2022

@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.

@ocaml ocaml locked and limited conversation to collaborators Jan 26, 2023
@nojb nojb converted this issue into discussion #11957 Jan 26, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

4 participants