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
I propose a default setting enhancement for lemma files and module imports for the kontrol build command. Current Requirement:
If a user wants to include project-specific lemmas, he must explicitly specify the lemmas file and module import on each build, like so:
kontrol build --require lemmas.k --module-import CronTwoTest:CRON-TWO-LEMMAS
Proposed Default Behavior:
The new behavior turns this configuration into a convention:
We let --require default to project-lemmas.k.
We let--module-import default to PROJECT-LEMMAS.
We auto-create project-lemmas.k with an empty PROJECT-LEMMAS module if not present. (Maybe we could even add a simple lemma here, so users have a template to start from).
We emit a warning/error if PROJECT-LEMMAS module is missing (e.g. because a user deleted it).
This simplifies the process, benefiting users by reducing repetitive command-line specifications.
The text was updated successfully, but these errors were encountered:
I propose a default setting enhancement for lemma files and module imports for the
kontrol build
command.Current Requirement:
If a user wants to include project-specific lemmas, he must explicitly specify the lemmas file and module import on each build, like so:
Proposed Default Behavior:
The new behavior turns this configuration into a convention:
--require
default toproject-lemmas.k
.--module-import
default toPROJECT-LEMMAS
.project-lemmas.k
with an emptyPROJECT-LEMMAS
module if not present. (Maybe we could even add a simple lemma here, so users have a template to start from).PROJECT-LEMMAS
module is missing (e.g. because a user deleted it).This simplifies the process, benefiting users by reducing repetitive command-line specifications.
The text was updated successfully, but these errors were encountered: