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
This has bothered me several times now since this ticket was filed.
I suggest we choose a convention and switch to it for the release following 2.10. In addition, let's allow settings to be changed by the old names for at least one release (and issue a warning that the old names are deprecated), but not show the alternate names in documentation, etc.
I suggest we go with camel case, as it fits more nicely with idiomatic cryptol naming, as - is not a valid identifier character.
Options are now all named in camelCase style. However, multiword
options may still be set using the old hypenated names as aliases,
so interaction scripts and the test suite do not have to be
changed. In addition, option lookup is altered to be case insensitive.
Thus, the canonical option name for the output SMT file when
an offline prover is selected is `smtFile`, which is what will
show up when running `:set` with no arguments, and what will be
suggested for tab-completion. However, the option may be set
using the strings `smtfile` `SMTFile`, `smt-file`, `SMT-file`, etc.
Fixes#656
Here are the names of all the settable options in the Cryptol REPL, as shown by tab completion:
Some are hyphenated, and some use camelCase. We should choose a single convention and use it consistently.
The text was updated successfully, but these errors were encountered: