You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the recent addition of Gbury/dolmen (that will allow alt-ergo to more input languages such as smtlib, tptp, etc...), we are considering potentially removing the support for dynlinked parsers, as this would allow to remove the entire legacy parsers and typechecker.
Before the removal, support for the native alt-ergo language as well as why3 will be added to dolmen so that no current capabilities of alt-ergo will be lost. However dolmen does not currently support dynlinking additional parsers, so we'd like to evaluate how much that feature is used, so please comment here if you are using dynlinked parsers or are planning on using them, ^^
The text was updated successfully, but these errors were encountered:
The support of custom parsers have been removed in #1251 and the deprecated AB-Why3 plugin was the only part of the code which used the Why3 parser. This plugin have been deprecated in v2.6.0 and removed in #1251 too.
Following the recent addition of Gbury/dolmen (that will allow alt-ergo to more input languages such as smtlib, tptp, etc...), we are considering potentially removing the support for dynlinked parsers, as this would allow to remove the entire legacy parsers and typechecker.
Before the removal, support for the native alt-ergo language as well as why3 will be added to dolmen so that no current capabilities of alt-ergo will be lost. However dolmen does not currently support dynlinking additional parsers, so we'd like to evaluate how much that feature is used, so please comment here if you are using dynlinked parsers or are planning on using them, ^^
The text was updated successfully, but these errors were encountered: