Skip to content

Commit 4c68d3c

Browse files
committed
remove comments
1 parent 3c50b1e commit 4c68d3c

File tree

1 file changed

+0
-15
lines changed

1 file changed

+0
-15
lines changed

CaseStudies/Velvet/Syntax.lean

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -355,21 +355,6 @@ elab_rules : command
355355

356356
if opts.getString (defVal := "unspecified") `loom.semantics.termination = "unspecified" then
357357
throwError "First, you need to specify the termination semantics using `set_option loom.semantics.termination <partial/total>`"
358-
359-
/- Now, depending on the solver option, we will locally define the `loom_solver` tactic. -/
360-
-- let solver := opts.getString (defVal := "grind") `loom.solver
361-
-- let thmCmd <- match solver with
362-
-- | "grind" =>
363-
-- /- In case of `grind` solver, we need to fetch the number of splits from the options first. -/
364-
-- let splits := Lean.Syntax.mkNatLit <| (opts.getNat (defVal := 20) `loom.solver.grind.splits)
365-
-- `(command|
366-
-- macro_rules | `(tactic| loom_solver) => do
367-
-- `(tactic| try grind ($(mkIdent `splits):ident := $splits)) in
368-
-- $thmCmd)
369-
-- | "custom" => pure thmCmd
370-
-- | _ =>
371-
-- /- This is the case of `cvc5` or `z3` solver. We also need to fetch the timeout from the options. -/
372-
-- `(command| macro_rules | `(tactic| loom_solver) => do `(tactic| loom_auto) in $thmCmd)
373358
trace[Loom] "{thmCmd}"
374359
match pv with
375360
| `(prove_correct_command| prove_correct) =>

0 commit comments

Comments
 (0)