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

[RFC] Removing the support for custom parser #643

Closed
Halbaroth opened this issue Jun 9, 2023 · 1 comment
Closed

[RFC] Removing the support for custom parser #643

Halbaroth opened this issue Jun 9, 2023 · 1 comment
Milestone

Comments

@Halbaroth
Copy link
Collaborator

As you know, Alt-Ergo will use Dolmen parser as a new frontend.
The Dolmen integration has been merged on next, see #491.

In the next release 2.5.0, Dolmen will be available through the option --frontend dolmen.
We plan to set Dolmen as the default parser in the release 2.6.0 and to remove the legacy parser in the release 2.7.0.

The current version of Alt-Ergo can use custom parser through the option --add-solver.

The only use I know of this feature is the custom parser of the AB-Why3 plugin see #642.

I think we can remove this feature.

@Halbaroth Halbaroth added this to the 2.7.0 milestone Jun 9, 2023
@Halbaroth Halbaroth changed the title [RFC] Remove support for custom parser [RFC] Removing the support for custom parser Jun 9, 2023
@Halbaroth
Copy link
Collaborator Author

Solved in #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

1 participant