diff options
author | Jason Gross <jgross@mit.edu> | 2019-03-14 16:14:45 -0400 |
---|---|---|
committer | Jason Gross <jasongross9@gmail.com> | 2019-03-31 09:31:15 -0400 |
commit | a8b4394093e61b050406ca952a6d017ad1c737e4 (patch) | |
tree | e75e2c0d33fd5a7fc4c46c3460b04530c30aa260 /src/Language.v | |
parent | b18cfd89e1e8760185d9f50dd777c1c8096cf807 (diff) |
Add constr_fail and constr_fail_with
Rather than taking the convention that failures during constr
construction emit a type error from `I : I` with the actual error
message `idtac`d above them (because Coq has no way to emit multiple
things on stderr), we instead factor everything through a new
`constr_fail` or `constr_fail_with msg_tac`, which emit more helpful
messages instructing the user to look in `*coq*` or to use `Fail`/`try`
to see the more informative error message. When we can make our own
version that does both `idtac` and `fail` (c.f.
https://github.com/coq/coq/issues/3913), then we can do something a bit
more sane, hopefully.
Diffstat (limited to 'src/Language.v')
-rw-r--r-- | src/Language.v | 24 |
1 files changed, 8 insertions, 16 deletions
diff --git a/src/Language.v b/src/Language.v index 81ca370db..4b112dfdb 100644 --- a/src/Language.v +++ b/src/Language.v @@ -16,6 +16,7 @@ Require Import Crypto.Util.Bool.Reflect. Require Import Crypto.Util.Notations. Require Import Crypto.Util.Tactics.RunTacticAsConstr. Require Import Crypto.Util.Tactics.DebugPrint. +Require Import Crypto.Util.Tactics.ConstrFail. Import Coq.Lists.List ListNotations. Local Open Scope bool_scope. Local Open Scope Z_scope. Module Compilers. @@ -64,10 +65,10 @@ Module Compilers. Ltac debug_leave_reify_in_context_success e ret := debug3 ltac:(fun _ => debug_leave_reify_success_idtac reify_in_context e ret). Ltac debug_leave_reify_in_context_failure e := let dummy := debug0 ltac:(fun _ => debug_leave_reify_failure_idtac reify_in_context e) in - constr:(I : I). + constr_fail. Ltac debug_leave_reify_base_type_failure e := let dummy := debug0 ltac:(fun _ => debug_leave_reify_failure_idtac reify_base_type e) in - constr:(I : I). + constr_fail. Tactic Notation "idtac_reify_in_context_case" ident(case) := idtac "reify_in_context:" case. Ltac debug_reify_in_context_case tac := @@ -392,10 +393,7 @@ Module Compilers. | zrange => type.zrange | interp (type.type_base ?T) => T | @einterp type interp (@Compilers.type.base type (type.type_base ?T)) => T - | _ => let __ := match goal with - | _ => fail 1 "Unrecognized type:" ty - end in - constr:(I : I) + | _ => constr_fail_with ltac:(fun _ => fail 1 "Unrecognized type:" ty) end. Ltac reify ty := let __ := Reify.debug_enter_reify_base_type ty in @@ -648,10 +646,7 @@ Module Compilers. lazymatch rb with | @Abs _ _ _ ?s ?d ?f => constr:(@LetIn base_type ident var s d ra f) - | ?rb => let __ := match goal with - | _ => fail 1 "Invalid non-Abs function reification of" b "to" rb - end in - constr:(I : I) + | ?rb => constr_fail_with ltac:(fun _ => fail 1 "Invalid non-Abs function reification of" b "to" rb) end | (fun x : ?T => ?f) => @@ -697,10 +692,7 @@ Module Compilers. remain. However, if this does come up, having a distinctive error message is much more useful for debugging than the generic "no matching clause" *) - let __ := match goal with - | _ => fail 1 "Failure to eliminate functional dependencies of" rf0 - end in - constr:(I : I) + constr_fail_with ltac:(fun _ => fail 1 "Failure to eliminate functional dependencies of" rf0) end end | _ @@ -738,7 +730,7 @@ Module Compilers. => let __ := match goal with | _ => fail 2 "Unrecognized term:" term' end in - constr:(I : I) + constr_fail end in match constr:(Set) with | _ => reify_rec term @@ -746,7 +738,7 @@ Module Compilers. | _ => idtac "Error: Failed to reify" term' "via unfolding"; fail 2 "Failed to reify" term' "via unfolding" end in - constr:(I : I) + constr_fail end) end) end |