Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
why3
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
119
Issues
119
List
Boards
Labels
Service Desk
Milestones
Merge Requests
16
Merge Requests
16
Operations
Operations
Incidents
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Why3
why3
Commits
d1d7174d
Commit
d1d7174d
authored
Feb 18, 2015
by
Guillaume Melquiond
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Encapsulate the tactic code into a module to avoid shadowing.
parent
48c6b603
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
10 deletions
+7
-10
src/coq-tactic/why3tac.ml4
src/coq-tactic/why3tac.ml4
+7
-10
No files found.
src/coq-tactic/why3tac.ml4
View file @
d1d7174d
...
...
@@ -96,14 +96,7 @@ DECLARE PLUGIN "why3tac"
END
(* forward reference because Why3 and Coq define the same modules,
thus shadowing each other *)
let why3tac_ref = ref (fun ?timelimit:_t _ -> Tactics.admit_as_an_axiom)
TACTIC EXTEND Why3
[ "why3" string(s) ] -> [ !why3tac_ref s ]
| [ "why3" string(s) "timelimit" integer(n) ] -> [ !why3tac_ref ~timelimit:n s ]
END
module Why3tac = struct
open Why3
open Call_provers
...
...
@@ -1338,8 +1331,12 @@ let why3tac ?timelimit s = Proofview.V82.tactic (why3tac ?timelimit s)
END
let () =
why3tac_ref := why3tac
end
TACTIC EXTEND Why3
[ "why3" string(s) ] -> [ Why3tac.why3tac s ]
| [ "why3" string(s) "timelimit" integer(n) ] -> [ Why3tac.why3tac ~timelimit:n s ]
END
(*
Local Variables:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment