-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Support for Coq v8.9 #4
Comments
That's all you need for diff --git a/plugin/src/ast_plugin.ml4 b/plugin/src/ast_plugin.ml4
index d2d93b2..697290b 100644
--- a/plugin/src/ast_plugin.ml4
+++ b/plugin/src/ast_plugin.ml4
@@ -3,7 +3,6 @@ DECLARE PLUGIN "ast_plugin"
open Format
open Constr
open Names
-open Stdarg
open Environ
open Declarations
open Univ
@@ -247,9 +246,10 @@ let build_universe_instance (i : Instance.t) =
* Build the AST for a sort
*)
let build_sort (s : Sorts.t) =
- let s_ast =
+ let s_ast = let open Sorts in
match s with
- | Prop _ -> if s = Sorts.prop then "Prop" else "Set"
+ | Prop -> "Prop"
+ | Set -> "Set"
| Type u -> build "Type" [build_universe u]
in build "Sort" [s_ast]
@@ -436,7 +436,7 @@ let build_cofix (funs : string list) (index : int) =
(*
* Get the body of a mutually inductive type
*)
-let lookup_mutind_body (i : mutual_inductive) (env : env) =
+let lookup_mutind_body (i : MutInd.t) (env : env) =
lookup_mind i env
(* |
Thanks for taking a look Emilio! It seems like |
I strongly suggest that plugins do follow the upstream branching scheme [which I do on my own projects] That is to say, This convention will be supported by Coq tools in the future [or course, people not wanting to follow it will have to define a few extra vars to indicate branch] |
Note that GitHub has a feature to set default branch shown on the main project page. |
I'm much afraid that this will make the plugin unusable, there is no choice other than branch. As of today I'm afraid that we are very far from having the same plugin code work in two versions of Coq. And there are big API changes planned which mean that this will be more true. Maybe after 8.10 things are more stable, but now I'm afraid we have strong reasons for the API changes. |
On Coq v8.9 (and also on Coq master, coq/coq@2917fd2cce3a28), the plugin fails to build with the following error:
The text was updated successfully, but these errors were encountered: