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.

Sign up for GitHub

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

Jump to bottom

cryptol-remote-api: Don't use verbose SBV settings #1379

Merged
merged 1 commit into from
Jul 8, 2022
Merged

cryptol-remote-api: Don't use verbose SBV settings #1379

merged 1 commit into from
Jul 8, 2022

Commits on Jul 8, 2022

  1. cryptol-remote-api: Don't use verbose SBV settings 

    We should try to match Cryptol's default settings when invoking the remote API,
but the `pcVerbose` value (`True`) didn't match the defaults. Changing this to
`False` should fix #1378. There is a separate question of whether remote API
users should be able to change this default, but for the time being, let's at
least be consistent between Cryptol's settings and the remote API's settings.
    @RyanGlScott
    RyanGlScott committed Jul 8, 2022
    Configuration menu
    Copy the full SHA
    3278540 View commit details
    Browse the repository at this point in the history