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

Disable all custom extensions in strict mode #1134

Open
bclement-ocp opened this issue May 27, 2024 · 3 comments
Open

Disable all custom extensions in strict mode #1134

bclement-ocp opened this issue May 27, 2024 · 3 comments
Labels

Comments

@bclement-ocp
Copy link
Collaborator

See #1133:

Currently, the --strict option only disables optimization. It should also disable extensions such as ae.round and bv2nat / int2bv.

@Halbaroth
Copy link
Collaborator

Halbaroth commented Aug 26, 2024

Do you know how to fix this issue. I quickly took a look to our codebase and Dolmen and we have no mechanism to disable Typer extension like bv2nat. We could disable bv2nat and ae.round only with the CLI flag --strict before the initialization of the typer.

If there is a way to create a local environment for the typer, we could add bv2nat in this environment when we process (set-option :strict-mode true) and remove it when we process (set-option :strict-mode false).
What's your opinion @Gbury ?

@bclement-ocp
Copy link
Collaborator Author

I think we can disable typer extensions, it should just be a matter of resetting the appropriate key on the state (it might not be exposed but we can expose it). Did not think about it more than that because this is likely one of the lowest priority issues we have.

@Halbaroth
Copy link
Collaborator

Sure, I think about it because I am writing documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants