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

Bison should support counterexample generation #12

Closed
andrewcmyers opened this issue Jul 7, 2019 · 4 comments
Closed

Bison should support counterexample generation #12

andrewcmyers opened this issue Jul 7, 2019 · 4 comments

Comments

@andrewcmyers
Copy link

andrewcmyers commented Jul 7, 2019

The classic problem with parser generators—and especially with LALR parser generators—is that it is often hard to diagnose what went wrong when there are conflicts. We developed some efficient algorithms for generating useful, concise counterexamples in our PLDI 2015 paper, "Finding Counterexamples from Parsing Conflicts". Unfortunately, we implemented it only in the CUP parser generator. It would be an excellent feature for Bison, though.

@akimd
Copy link
Owner

akimd commented Jul 13, 2019

Hi Andrew,
Yes, it's an excellent idea, we should definitely do something like this. And actually, contributions are most welcome :)
Cheers!

@Xaec6
Copy link
Contributor

Xaec6 commented Sep 25, 2019

Hi Akim,
As an update, I'm currently working on implementing this under professor Myers. It should be done in a few months.

@akimd
Copy link
Owner

akimd commented Oct 15, 2019

Hi Vincent,
That's a wonderful piece of news! Do not hesitate to interact with the Bison team (bison-patches at gnu.org). Cheers!

@akimd
Copy link
Owner

akimd commented May 23, 2020

I'm very happy to close this issue. While the feature is not released yet, there is no doubt it will be (it is now part of the master branch of Bison). @Xaec6 has reformatted his work to comply with our standards, and since then is committed to address any report about the feature, as can be seen in the Bison Patches Archive.

Many many thanks to both @andrewcmyers and @Xaec6.

Cheers!

@akimd akimd closed this as completed May 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants