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

Get rid of the legacy front-end? #556

Closed
hra687261 opened this issue Apr 2, 2023 · 4 comments
Closed

Get rid of the legacy front-end? #556

hra687261 opened this issue Apr 2, 2023 · 4 comments

Comments

@hra687261
Copy link
Contributor

Alt-Ergo should only have one front-end, it's very annoying to have to do any changes to the front-end twice, once in Alt-Ergo, once in Dolmen.
If more testing needs to be done, then it should be a priority to do it and fix the eventual issues that would come up with switching to Dolmen.

@Halbaroth
Copy link
Collaborator

Halbaroth commented Apr 3, 2023

I totally agree that we should get rid of it as soon as possible. But we should be sure the actually parser in Dolmen behaves closely like the legacy one. We have very few files in the native input format, which means we didn't test it properly.
Maybe, we could produce some tests for Dolmen before removing the legacy parser?

We should also check the support of psmt in Dolmen.

@hra687261
Copy link
Contributor Author

We can probably generate a good amount of them from Why3's test-suite.
Also once printers become available in Dolmen we can translate some of them.
But I think it should be a priority, because it significantly slows down development whenever someones touches the frontend.

@bclement-ocp
Copy link
Collaborator

Blocked by #585 and #586

@hra687261
Copy link
Contributor Author

Closing this issue since the legacy front end was removed with #1251

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

3 participants