adamc@26: (* Copyright (c) 2008, Adam Chlipala
adamc@26: *
adamc@26: * This work is licensed under a
adamc@26: * Creative Commons Attribution-Noncommercial-No Derivative Works 3.0
adamc@26: * Unported License.
adamc@26: * The license text is available at:
adamc@26: * http://creativecommons.org/licenses/by-nc-nd/3.0/
adamc@26: *)
adamc@26:
adamc@26: (* begin hide *)
adamc@26: Require Import List.
adamc@26:
adamc@26: Require Import Tactics.
adamc@26:
adamc@26: Set Implicit Arguments.
adamc@26: (* end hide *)
adamc@26:
adamc@26:
adamc@74: (** %\part{Basic Programming and Proving}
adamc@74:
adamc@74: \chapter{Introducing Inductive Types}% *)
adamc@26:
adamc@45: (** In a sense, CIC is built from just two relatively straightforward features: function types and inductive types. From this modest foundation, we can prove effectively all of the theorems of math and carry out effectively all program verifications, with enough effort expended. This chapter introduces induction and recursion for functional programming in Coq. *)
adamc@26:
adamc@26:
adamc@26: (** * Enumerations *)
adamc@26:
adamc@26: (** Coq inductive types generalize the algebraic datatypes found in Haskell and ML. Confusingly enough, inductive types also generalize generalized algebraic datatypes (GADTs), by adding the possibility for type dependency. Even so, it is worth backing up from the examples of the last chapter and going over basic, algebraic datatype uses of inductive datatypes, because the chance to prove things about the values of these types adds new wrinkles beyond usual practice in Haskell and ML.
adamc@26:
adamc@26: The singleton type [unit] is an inductive type: *)
adamc@26:
adamc@26: Inductive unit : Set :=
adamc@26: | tt.
adamc@26:
adamc@26: (** This vernacular command defines a new inductive type [unit] whose only value is [tt], as we can see by checking the types of the two identifiers: *)
adamc@26:
adamc@26: Check unit.
adamc@26: (** [[
adamc@26:
adamc@26: unit : Set
adamc@26: ]] *)
adamc@26: Check tt.
adamc@26: (** [[
adamc@26:
adamc@26: tt : unit
adamc@26: ]] *)
adamc@26:
adamc@26: (** We can prove that [unit] is a genuine singleton type. *)
adamc@26:
adamc@26: Theorem unit_singleton : forall x : unit, x = tt.
adamc@26: (** The important thing about an inductive type is, unsurprisingly, that you can do induction over its values, and induction is the key to proving this theorem. We ask to proceed by induction on the variable [x]. *)
adamc@41: (* begin thide *)
adamc@26: induction x.
adamc@26: (** The goal changes to: [[
adamc@26:
adamc@26: tt = tt
adamc@26: ]] *)
adamc@26: (** ...which we can discharge trivially. *)
adamc@26: reflexivity.
adamc@26: Qed.
adamc@41: (* end thide *)
adamc@26:
adamc@26: (** It seems kind of odd to write a proof by induction with no inductive hypotheses. We could have arrived at the same result by beginning the proof with: [[
adamc@26:
adamc@26: destruct x.
adamc@26: ...which corresponds to "proof by case analysis" in classical math. For non-recursive inductive types, the two tactics will always have identical behavior. Often case analysis is sufficient, even in proofs about recursive types, and it is nice to avoid introducing unneeded induction hypotheses.
adamc@26:
adamc@26: What exactly %\textit{%##is##%}% the induction principle for [unit]? We can ask Coq: *)
adamc@26:
adamc@26: Check unit_ind.
adamc@26: (** [[
adamc@26:
adamc@26: unit_ind : forall P : unit -> Prop, P tt -> forall u : unit, P u
adamc@26: ]]
adamc@26:
adamc@26: Every [Inductive] command defining a type [T] also defines an induction principle named [T_ind]. Coq follows the Curry-Howard correspondence and includes the ingredients of programming and proving in the same single syntactic class. Thus, our type, operations over it, and principles for reasoning about it all live in the same language and are described by the same type system. The key to telling what is a program and what is a proof lies in the distinction between the type [Prop], which appears in our induction principle; and the type [Set], which we have seen a few times already.
adamc@26:
adamc@26: The convention goes like this: [Set] is the type of normal types, and the values of such types are programs. [Prop] is the type of logical propositions, and the values of such types are proofs. Thus, an induction principle has a type that shows us that it is a function for building proofs.
adamc@26:
adamc@26: Specifically, [unit_ind] quantifies over a predicate [P] over [unit] values. If we can present a proof that [P] holds of [tt], then we are rewarded with a proof that [P] holds for any value [u] of type [unit]. In our last proof, the predicate was [(fun u : unit => u = tt)].
adamc@26:
adamc@26: %\medskip%
adamc@26:
adamc@26: We can define an inductive type even simpler than [unit]: *)
adamc@26:
adamc@26: Inductive Empty_set : Set := .
adamc@26:
adamc@26: (** [Empty_set] has no elements. We can prove fun theorems about it: *)
adamc@26:
adamc@26: Theorem the_sky_is_falling : forall x : Empty_set, 2 + 2 = 5.
adamc@41: (* begin thide *)
adamc@26: destruct 1.
adamc@26: Qed.
adamc@41: (* end thide *)
adamc@26:
adamc@32: (** Because [Empty_set] has no elements, the fact of having an element of this type implies anything. We use [destruct 1] instead of [destruct x] in the proof because unused quantified variables are relegated to being referred to by number. (There is a good reason for this, related to the unity of quantifiers and implication. An implication is just a quantification over a proof, where the quantified variable is never used. It generally makes more sense to refer to implication hypotheses by number than by name, and Coq treats our quantifier over an unused variable as an implication in determining the proper behavior.)
adamc@26:
adamc@26: We can see the induction principle that made this proof so easy: *)
adamc@26:
adamc@26: Check Empty_set_ind.
adamc@26: (** [[
adamc@26:
adamc@26: Empty_set_ind : forall (P : Empty_set -> Prop) (e : Empty_set), P e
adamc@26: ]]
adamc@26:
adamc@26: In other words, any predicate over values from the empty set holds vacuously of every such element. In the last proof, we chose the predicate [(fun _ : Empty_set => 2 + 2 = 5)].
adamc@26:
adamc@26: We can also apply this get-out-of-jail-free card programmatically. Here is a lazy way of converting values of [Empty_set] to values of [unit]: *)
adamc@26:
adamc@26: Definition e2u (e : Empty_set) : unit := match e with end.
adamc@26:
adamc@26: (** We employ [match] pattern matching as in the last chapter. Since we match on a value whose type has no constructors, there is no need to provide any branches.
adamc@26:
adamc@26: %\medskip%
adamc@26:
adamc@26: Moving up the ladder of complexity, we can define the booleans: *)
adamc@26:
adamc@26: Inductive bool : Set :=
adamc@26: | true
adamc@26: | false.
adamc@26:
adamc@26: (** We can use less vacuous pattern matching to define boolean negation. *)
adamc@26:
adamc@26: Definition not (b : bool) : bool :=
adamc@26: match b with
adamc@26: | true => false
adamc@26: | false => true
adamc@26: end.
adamc@26:
adamc@27: (** An alternative definition desugars to the above: *)
adamc@27:
adamc@27: Definition not' (b : bool) : bool :=
adamc@27: if b then false else true.
adamc@27:
adamc@26: (** We might want to prove that [not] is its own inverse operation. *)
adamc@26:
adamc@26: Theorem not_inverse : forall b : bool, not (not b) = b.
adamc@41: (* begin thide *)
adamc@26: destruct b.
adamc@26:
adamc@26: (** After we case analyze on [b], we are left with one subgoal for each constructor of [bool].
adamc@26:
adamc@26: [[
adamc@26:
adamc@26: 2 subgoals
adamc@26:
adamc@26: ============================
adamc@26: not (not true) = true
adamc@26: ]]
adamc@26:
adamc@26: [[
adamc@26: subgoal 2 is:
adamc@26: not (not false) = false
adamc@26: ]]
adamc@26:
adamc@26: The first subgoal follows by Coq's rules of computation, so we can dispatch it easily: *)
adamc@26:
adamc@26: reflexivity.
adamc@26:
adamc@26: (** Likewise for the second subgoal, so we can restart the proof and give a very compact justification. *)
adamc@26:
adamc@26: Restart.
adamc@26: destruct b; reflexivity.
adamc@26: Qed.
adamc@41: (* end thide *)
adamc@27:
adamc@27: (** Another theorem about booleans illustrates another useful tactic. *)
adamc@27:
adamc@27: Theorem not_ineq : forall b : bool, not b <> b.
adamc@41: (* begin thide *)
adamc@27: destruct b; discriminate.
adamc@27: Qed.
adamc@41: (* end thide *)
adamc@27:
adamc@27: (** [discriminate] is used to prove that two values of an inductive type are not equal, whenever the values are formed with different constructors. In this case, the different constructors are [true] and [false].
adamc@27:
adamc@27: At this point, it is probably not hard to guess what the underlying induction principle for [bool] is. *)
adamc@27:
adamc@27: Check bool_ind.
adamc@27: (** [[
adamc@27:
adamc@27: bool_ind : forall P : bool -> Prop, P true -> P false -> forall b : bool, P b
adamc@27: ]] *)
adamc@28:
adamc@28:
adamc@28: (** * Simple Recursive Types *)
adamc@28:
adamc@28: (** The natural numbers are the simplest common example of an inductive type that actually deserves the name. *)
adamc@28:
adamc@28: Inductive nat : Set :=
adamc@28: | O : nat
adamc@28: | S : nat -> nat.
adamc@28:
adamc@28: (** [O] is zero, and [S] is the successor function, so that [0] is syntactic sugar for [O], [1] for [S O], [2] for [S (S O)], and so on.
adamc@28:
adamc@28: Pattern matching works as we demonstrated in the last chapter: *)
adamc@28:
adamc@28: Definition isZero (n : nat) : bool :=
adamc@28: match n with
adamc@28: | O => true
adamc@28: | S _ => false
adamc@28: end.
adamc@28:
adamc@28: Definition pred (n : nat) : nat :=
adamc@28: match n with
adamc@28: | O => O
adamc@28: | S n' => n'
adamc@28: end.
adamc@28:
adamc@28: (** We can prove theorems by case analysis: *)
adamc@28:
adamc@28: Theorem S_isZero : forall n : nat, isZero (pred (S (S n))) = false.
adamc@41: (* begin thide *)
adamc@28: destruct n; reflexivity.
adamc@28: Qed.
adamc@41: (* end thide *)
adamc@28:
adamc@28: (** We can also now get into genuine inductive theorems. First, we will need a recursive function, to make things interesting. *)
adamc@28:
adamc@28: Fixpoint plus (n m : nat) {struct n} : nat :=
adamc@28: match n with
adamc@28: | O => m
adamc@28: | S n' => S (plus n' m)
adamc@28: end.
adamc@28:
adamc@28: (** Recall that [Fixpoint] is Coq's mechanism for recursive function definitions, and that the [{struct n}] annotation is noting which function argument decreases structurally at recursive calls.
adamc@28:
adamc@28: Some theorems about [plus] can be proved without induction. *)
adamc@28:
adamc@28: Theorem O_plus_n : forall n : nat, plus O n = n.
adamc@41: (* begin thide *)
adamc@28: intro; reflexivity.
adamc@28: Qed.
adamc@41: (* end thide *)
adamc@28:
adamc@28: (** Coq's computation rules automatically simplify the application of [plus]. If we just reverse the order of the arguments, though, this no longer works, and we need induction. *)
adamc@28:
adamc@28: Theorem n_plus_O : forall n : nat, plus n O = n.
adamc@41: (* begin thide *)
adamc@28: induction n.
adamc@28:
adamc@28: (** Our first subgoal is [plus O O = O], which %\textit{%##is##%}% trivial by computation. *)
adamc@28:
adamc@28: reflexivity.
adamc@28:
adamc@28: (** Our second subgoal is more work and also demonstrates our first inductive hypothesis.
adamc@28:
adamc@28: [[
adamc@28:
adamc@28: n : nat
adamc@28: IHn : plus n O = n
adamc@28: ============================
adamc@28: plus (S n) O = S n
adamc@28: ]]
adamc@28:
adamc@28: We can start out by using computation to simplify the goal as far as we can. *)
adamc@28:
adamc@28: simpl.
adamc@28:
adamc@28: (** Now the conclusion is [S (plus n O) = S n]. Using our inductive hypothesis: *)
adamc@28:
adamc@28: rewrite IHn.
adamc@28:
adamc@28: (** ...we get a trivial conclusion [S n = S n]. *)
adamc@28:
adamc@28: reflexivity.
adamc@28:
adamc@28: (** Not much really went on in this proof, so the [crush] tactic from the [Tactics] module can prove this theorem automatically. *)
adamc@28:
adamc@28: Restart.
adamc@28: induction n; crush.
adamc@28: Qed.
adamc@41: (* end thide *)
adamc@28:
adamc@28: (** We can check out the induction principle at work here: *)
adamc@28:
adamc@28: Check nat_ind.
adamc@28: (** [[
adamc@28:
adamc@28: nat_ind : forall P : nat -> Prop,
adamc@28: P O -> (forall n : nat, P n -> P (S n)) -> forall n : nat, P n
adamc@28: ]]
adamc@28:
adamc@28: Each of the two cases of our last proof came from the type of one of the arguments to [nat_ind]. We chose [P] to be [(fun n : nat => plus n O = n)]. The first proof case corresponded to [P O], and the second case to [(forall n : nat, P n -> P (S n))]. The free variable [n] and inductive hypothesis [IHn] came from the argument types given here.
adamc@28:
adamc@28: Since [nat] has a constructor that takes an argument, we may sometimes need to know that that constructor is injective. *)
adamc@28:
adamc@28: Theorem S_inj : forall n m : nat, S n = S m -> n = m.
adamc@41: (* begin thide *)
adamc@28: injection 1; trivial.
adamc@28: Qed.
adamc@41: (* end thide *)
adamc@28:
adamc@28: (** [injection] refers to a premise by number, adding new equalities between the corresponding arguments of equated terms that are formed with the same constructor. We end up needing to prove [n = m -> n = m], so it is unsurprising that a tactic named [trivial] is able to finish the proof.
adamc@28:
adamc@29: There is also a very useful tactic called [congruence] that can prove this theorem immediately. [congruence] generalizes [discriminate] and [injection], and it also adds reasoning about the general properties of equality, such as that a function returns equal results on equal arguments. That is, [congruence] is a %\textit{%##complete decision procedure for the theory of equality and uninterpreted functions##%}%, plus some smarts about inductive types.
adamc@29:
adamc@29: %\medskip%
adamc@29:
adamc@29: We can define a type of lists of natural numbers. *)
adamc@29:
adamc@29: Inductive nat_list : Set :=
adamc@29: | NNil : nat_list
adamc@29: | NCons : nat -> nat_list -> nat_list.
adamc@29:
adamc@29: (** Recursive definitions are straightforward extensions of what we have seen before. *)
adamc@29:
adamc@29: Fixpoint nlength (ls : nat_list) : nat :=
adamc@29: match ls with
adamc@29: | NNil => O
adamc@29: | NCons _ ls' => S (nlength ls')
adamc@29: end.
adamc@29:
adamc@29: Fixpoint napp (ls1 ls2 : nat_list) {struct ls1} : nat_list :=
adamc@29: match ls1 with
adamc@29: | NNil => ls2
adamc@29: | NCons n ls1' => NCons n (napp ls1' ls2)
adamc@29: end.
adamc@29:
adamc@29: (** Inductive theorem proving can again be automated quite effectively. *)
adamc@29:
adamc@29: Theorem nlength_napp : forall ls1 ls2 : nat_list, nlength (napp ls1 ls2)
adamc@29: = plus (nlength ls1) (nlength ls2).
adamc@41: (* begin thide *)
adamc@29: induction ls1; crush.
adamc@29: Qed.
adamc@41: (* end thide *)
adamc@29:
adamc@29: Check nat_list_ind.
adamc@29: (** [[
adamc@29:
adamc@29: nat_list_ind
adamc@29: : forall P : nat_list -> Prop,
adamc@29: P NNil ->
adamc@29: (forall (n : nat) (n0 : nat_list), P n0 -> P (NCons n n0)) ->
adamc@29: forall n : nat_list, P n
adamc@29: ]]
adamc@29:
adamc@29: %\medskip%
adamc@29:
adamc@29: In general, we can implement any "tree" types as inductive types. For example, here are binary trees of naturals. *)
adamc@29:
adamc@29: Inductive nat_btree : Set :=
adamc@29: | NLeaf : nat_btree
adamc@29: | NNode : nat_btree -> nat -> nat_btree -> nat_btree.
adamc@29:
adamc@29: Fixpoint nsize (tr : nat_btree) : nat :=
adamc@29: match tr with
adamc@35: | NLeaf => S O
adamc@29: | NNode tr1 _ tr2 => plus (nsize tr1) (nsize tr2)
adamc@29: end.
adamc@29:
adamc@29: Fixpoint nsplice (tr1 tr2 : nat_btree) {struct tr1} : nat_btree :=
adamc@29: match tr1 with
adamc@35: | NLeaf => NNode tr2 O NLeaf
adamc@29: | NNode tr1' n tr2' => NNode (nsplice tr1' tr2) n tr2'
adamc@29: end.
adamc@29:
adamc@29: Theorem plus_assoc : forall n1 n2 n3 : nat, plus (plus n1 n2) n3 = plus n1 (plus n2 n3).
adamc@41: (* begin thide *)
adamc@29: induction n1; crush.
adamc@29: Qed.
adamc@41: (* end thide *)
adamc@29:
adamc@29: Theorem nsize_nsplice : forall tr1 tr2 : nat_btree, nsize (nsplice tr1 tr2)
adamc@29: = plus (nsize tr2) (nsize tr1).
adamc@41: (* begin thide *)
adamc@29: Hint Rewrite n_plus_O plus_assoc : cpdt.
adamc@29:
adamc@29: induction tr1; crush.
adamc@29: Qed.
adamc@41: (* end thide *)
adamc@29:
adamc@29: Check nat_btree_ind.
adamc@29: (** [[
adamc@29:
adamc@29: nat_btree_ind
adamc@29: : forall P : nat_btree -> Prop,
adamc@29: P NLeaf ->
adamc@29: (forall n : nat_btree,
adamc@29: P n -> forall (n0 : nat) (n1 : nat_btree), P n1 -> P (NNode n n0 n1)) ->
adamc@29: forall n : nat_btree, P n
adamc@29: ]] *)
adamc@30:
adamc@30:
adamc@30: (** * Parameterized Types *)
adamc@30:
adamc@30: (** We can also define polymorphic inductive types, as with algebraic datatypes in Haskell and ML. *)
adamc@30:
adamc@30: Inductive list (T : Set) : Set :=
adamc@30: | Nil : list T
adamc@30: | Cons : T -> list T -> list T.
adamc@30:
adamc@30: Fixpoint length T (ls : list T) : nat :=
adamc@30: match ls with
adamc@30: | Nil => O
adamc@30: | Cons _ ls' => S (length ls')
adamc@30: end.
adamc@30:
adamc@30: Fixpoint app T (ls1 ls2 : list T) {struct ls1} : list T :=
adamc@30: match ls1 with
adamc@30: | Nil => ls2
adamc@30: | Cons x ls1' => Cons x (app ls1' ls2)
adamc@30: end.
adamc@30:
adamc@30: Theorem length_app : forall T (ls1 ls2 : list T), length (app ls1 ls2)
adamc@30: = plus (length ls1) (length ls2).
adamc@41: (* begin thide *)
adamc@30: induction ls1; crush.
adamc@30: Qed.
adamc@41: (* end thide *)
adamc@30:
adamc@30: (** There is a useful shorthand for writing many definitions that share the same parameter, based on Coq's %\textit{%##section##%}% mechanism. The following block of code is equivalent to the above: *)
adamc@30:
adamc@30: (* begin hide *)
adamc@30: Reset list.
adamc@30: (* end hide *)
adamc@30:
adamc@30: Section list.
adamc@30: Variable T : Set.
adamc@30:
adamc@30: Inductive list : Set :=
adamc@30: | Nil : list
adamc@30: | Cons : T -> list -> list.
adamc@30:
adamc@30: Fixpoint length (ls : list) : nat :=
adamc@30: match ls with
adamc@30: | Nil => O
adamc@30: | Cons _ ls' => S (length ls')
adamc@30: end.
adamc@30:
adamc@30: Fixpoint app (ls1 ls2 : list) {struct ls1} : list :=
adamc@30: match ls1 with
adamc@30: | Nil => ls2
adamc@30: | Cons x ls1' => Cons x (app ls1' ls2)
adamc@30: end.
adamc@30:
adamc@30: Theorem length_app : forall ls1 ls2 : list, length (app ls1 ls2)
adamc@30: = plus (length ls1) (length ls2).
adamc@41: (* begin thide *)
adamc@30: induction ls1; crush.
adamc@30: Qed.
adamc@41: (* end thide *)
adamc@30: End list.
adamc@30:
adamc@35: (* begin hide *)
adamc@35: Implicit Arguments Nil [T].
adamc@35: (* end hide *)
adamc@35:
adamc@30: (** After we end the section, the [Variable]s we used are added as extra function parameters for each defined identifier, as needed. *)
adamc@30:
adamc@30: Check list.
adamc@30: (** [[
adamc@30:
adamc@30: list
adamc@30: : Set -> Set
adamc@30: ]] *)
adamc@30:
adamc@30: Check Cons.
adamc@30: (** [[
adamc@30:
adamc@30: Cons
adamc@30: : forall T : Set, T -> list T -> list T
adamc@30: ]] *)
adamc@30:
adamc@30: Check length.
adamc@30: (** [[
adamc@30:
adamc@30: length
adamc@30: : forall T : Set, list T -> nat
adamc@30: ]]
adamc@30:
adamc@30: The extra parameter [T] is treated as a new argument to the induction principle, too. *)
adamc@30:
adamc@30: Check list_ind.
adamc@30: (** [[
adamc@30:
adamc@30: list_ind
adamc@30: : forall (T : Set) (P : list T -> Prop),
adamc@30: P (Nil T) ->
adamc@30: (forall (t : T) (l : list T), P l -> P (Cons t l)) ->
adamc@30: forall l : list T, P l
adamc@30: ]]
adamc@30:
adamc@30: Thus, even though we just saw that [T] is added as an extra argument to the constructor [Cons], there is no quantifier for [T] in the type of the inductive case like there is for each of the other arguments. *)
adamc@31:
adamc@31:
adamc@31: (** * Mutually Inductive Types *)
adamc@31:
adamc@31: (** We can define inductive types that refer to each other: *)
adamc@31:
adamc@31: Inductive even_list : Set :=
adamc@31: | ENil : even_list
adamc@31: | ECons : nat -> odd_list -> even_list
adamc@31:
adamc@31: with odd_list : Set :=
adamc@31: | OCons : nat -> even_list -> odd_list.
adamc@31:
adamc@31: Fixpoint elength (el : even_list) : nat :=
adamc@31: match el with
adamc@31: | ENil => O
adamc@31: | ECons _ ol => S (olength ol)
adamc@31: end
adamc@31:
adamc@31: with olength (ol : odd_list) : nat :=
adamc@31: match ol with
adamc@31: | OCons _ el => S (elength el)
adamc@31: end.
adamc@31:
adamc@31: Fixpoint eapp (el1 el2 : even_list) {struct el1} : even_list :=
adamc@31: match el1 with
adamc@31: | ENil => el2
adamc@31: | ECons n ol => ECons n (oapp ol el2)
adamc@31: end
adamc@31:
adamc@31: with oapp (ol : odd_list) (el : even_list) {struct ol} : odd_list :=
adamc@31: match ol with
adamc@31: | OCons n el' => OCons n (eapp el' el)
adamc@31: end.
adamc@31:
adamc@31: (** Everything is going roughly the same as in past examples, until we try to prove a theorem similar to those that came before. *)
adamc@31:
adamc@31: Theorem elength_eapp : forall el1 el2 : even_list,
adamc@31: elength (eapp el1 el2) = plus (elength el1) (elength el2).
adamc@41: (* begin thide *)
adamc@31: induction el1; crush.
adamc@31:
adamc@31: (** One goal remains: [[
adamc@31:
adamc@31: n : nat
adamc@31: o : odd_list
adamc@31: el2 : even_list
adamc@31: ============================
adamc@31: S (olength (oapp o el2)) = S (plus (olength o) (elength el2))
adamc@31: ]]
adamc@31:
adamc@31: We have no induction hypothesis, so we cannot prove this goal without starting another induction, which would reach a similar point, sending us into a futile infinite chain of inductions. The problem is that Coq's generation of [T_ind] principles is incomplete. We only get non-mutual induction principles generated by default. *)
adamc@31:
adamc@31: Abort.
adamc@31: Check even_list_ind.
adamc@31: (** [[
adamc@31:
adamc@31: even_list_ind
adamc@31: : forall P : even_list -> Prop,
adamc@31: P ENil ->
adamc@31: (forall (n : nat) (o : odd_list), P (ECons n o)) ->
adamc@31: forall e : even_list, P e
adamc@31: ]]
adamc@31:
adamc@31: We see that no inductive hypotheses are included anywhere in the type. To get them, we must ask for mutual principles as we need them, using the [Scheme] command. *)
adamc@31:
adamc@31: Scheme even_list_mut := Induction for even_list Sort Prop
adamc@31: with odd_list_mut := Induction for odd_list Sort Prop.
adamc@31:
adamc@31: Check even_list_mut.
adamc@31: (** [[
adamc@31:
adamc@31: even_list_mut
adamc@31: : forall (P : even_list -> Prop) (P0 : odd_list -> Prop),
adamc@31: P ENil ->
adamc@31: (forall (n : nat) (o : odd_list), P0 o -> P (ECons n o)) ->
adamc@31: (forall (n : nat) (e : even_list), P e -> P0 (OCons n e)) ->
adamc@31: forall e : even_list, P e
adamc@31: ]]
adamc@31:
adamc@31: This is the principle we wanted in the first place. There is one more wrinkle left in using it: the [induction] tactic will not apply it for us automatically. It will be helpful to look at how to prove one of our past examples without using [induction], so that we can then generalize the technique to mutual inductive types. *)
adamc@31:
adamc@31: Theorem n_plus_O' : forall n : nat, plus n O = n.
adamc@31: apply (nat_ind (fun n => plus n O = n)); crush.
adamc@31: Qed.
adamc@31:
adamc@31: (** From this example, we can see that [induction] is not magic. It only does some bookkeeping for us to make it easy to apply a theorem, which we can do directly with the [apply] tactic. We apply not just an identifier but a partial application of it, specifying the predicate we mean to prove holds for all naturals.
adamc@31:
adamc@31: This technique generalizes to our mutual example: *)
adamc@31:
adamc@31: Theorem elength_eapp : forall el1 el2 : even_list,
adamc@31: elength (eapp el1 el2) = plus (elength el1) (elength el2).
adamc@41:
adamc@31: apply (even_list_mut
adamc@31: (fun el1 : even_list => forall el2 : even_list,
adamc@31: elength (eapp el1 el2) = plus (elength el1) (elength el2))
adamc@31: (fun ol : odd_list => forall el : even_list,
adamc@31: olength (oapp ol el) = plus (olength ol) (elength el))); crush.
adamc@31: Qed.
adamc@41: (* end thide *)
adamc@31:
adamc@31: (** We simply need to specify two predicates, one for each of the mutually inductive types. In general, it would not be a good idea to assume that a proof assistant could infer extra predicates, so this way of applying mutual induction is about as straightforward as we could hope for. *)
adamc@33:
adamc@33:
adamc@33: (** * Reflexive Types *)
adamc@33:
adamc@33: (** A kind of inductive type called a %\textit{%##reflexive type##%}% is defined in terms of functions that have the type being defined as their range. One very useful class of examples is in modeling variable binders. For instance, here is a type for encoding the syntax of a subset of first-order logic: *)
adamc@33:
adamc@33: Inductive formula : Set :=
adamc@33: | Eq : nat -> nat -> formula
adamc@33: | And : formula -> formula -> formula
adamc@33: | Forall : (nat -> formula) -> formula.
adamc@33:
adamc@33: (** Our kinds of formulas are equalities between naturals, conjunction, and universal quantification over natural numbers. We avoid needing to include a notion of "variables" in our type, by using Coq functions to encode quantification. For instance, here is the encoding of [forall x : nat, x = x]: *)
adamc@33:
adamc@33: Example forall_refl : formula := Forall (fun x => Eq x x).
adamc@33:
adamc@33: (** We can write recursive functions over reflexive types quite naturally. Here is one translating our formulas into native Coq propositions. *)
adamc@33:
adamc@33: Fixpoint formulaDenote (f : formula) : Prop :=
adamc@33: match f with
adamc@33: | Eq n1 n2 => n1 = n2
adamc@33: | And f1 f2 => formulaDenote f1 /\ formulaDenote f2
adamc@33: | Forall f' => forall n : nat, formulaDenote (f' n)
adamc@33: end.
adamc@33:
adamc@33: (** We can also encode a trivial formula transformation that swaps the order of equality and conjunction operands. *)
adamc@33:
adamc@33: Fixpoint swapper (f : formula) : formula :=
adamc@33: match f with
adamc@33: | Eq n1 n2 => Eq n2 n1
adamc@33: | And f1 f2 => And (swapper f2) (swapper f1)
adamc@33: | Forall f' => Forall (fun n => swapper (f' n))
adamc@33: end.
adamc@33:
adamc@33: (** It is helpful to prove that this transformation does not make true formulas false. *)
adamc@33:
adamc@33: Theorem swapper_preserves_truth : forall f, formulaDenote f -> formulaDenote (swapper f).
adamc@41: (* begin thide *)
adamc@33: induction f; crush.
adamc@33: Qed.
adamc@41: (* end thide *)
adamc@33:
adamc@33: (** We can take a look at the induction principle behind this proof. *)
adamc@33:
adamc@33: Check formula_ind.
adamc@33: (** [[
adamc@33:
adamc@33: formula_ind
adamc@33: : forall P : formula -> Prop,
adamc@33: (forall n n0 : nat, P (Eq n n0)) ->
adamc@33: (forall f0 : formula,
adamc@33: P f0 -> forall f1 : formula, P f1 -> P (And f0 f1)) ->
adamc@33: (forall f1 : nat -> formula,
adamc@33: (forall n : nat, P (f1 n)) -> P (Forall f1)) ->
adamc@33: forall f2 : formula, P f2
adamc@33: ]] *)
adamc@33:
adamc@33: (** Focusing on the [Forall] case, which comes third, we see that we are allowed to assume that the theorem holds %\textit{%##for any application of the argument function [f1]##%}%. That is, Coq induction principles do not follow a simple rule that the textual representations of induction variables must get shorter in appeals to induction hypotheses. Luckily for us, the people behind the metatheory of Coq have verified that this flexibility does not introduce unsoundness.
adamc@33:
adamc@33: %\medskip%
adamc@33:
adamc@33: Up to this point, we have seen how to encode in Coq more and more of what is possible with algebraic datatypes in Haskell and ML. This may have given the inaccurate impression that inductive types are a strict extension of algebraic datatypes. In fact, Coq must rule out some types allowed by Haskell and ML, for reasons of soundness. Reflexive types provide our first good example of such a case.
adamc@33:
adamc@33: Given our last example of an inductive type, many readers are probably eager to try encoding the syntax of lambda calculus. Indeed, the function-based representation technique that we just used, called %\textit{%##higher-order abstract syntax (HOAS)##%}%, is the representation of choice for lambda calculi in Twelf and in many applications implemented in Haskell and ML. Let us try to import that choice to Coq: *)
adamc@33:
adamc@33: (** [[
adamc@33:
adamc@33: Inductive term : Set :=
adamc@33: | App : term -> term -> term
adamc@33: | Abs : (term -> term) -> term.
adamc@33:
adamc@33: [[
adamc@33: Error: Non strictly positive occurrence of "term" in "(term -> term) -> term"
adamc@33: ]]
adamc@33:
adamc@33: We have run afoul of the %\textit{%##strict positivity requirement##%}% for inductive definitions, which says that the type being defined may not occur to the left of an arrow in the type of a constructor argument. It is important that the type of a constructor is viewed in terms of a series of arguments and a result, since obviously we need recursive occurrences to the lefts of the outermost arrows if we are to have recursive occurrences at all.
adamc@33:
adamc@33: Why must Coq enforce this restriction? Imagine that our last definition had been accepted, allowing us to write this function:
adamc@33:
adamc@33: [[
adamc@33: Definition uhoh (t : term) : term :=
adamc@33: match t with
adamc@33: | Abs f => f t
adamc@33: | _ => t
adamc@33: end.
adamc@33:
adamc@33: Using an informal idea of Coq's semantics, it is easy to verify that the application [uhoh (Abs uhoh)] will run forever. This would be a mere curiosity in OCaml and Haskell, where non-termination is commonplace, though the fact that we have a non-terminating program without explicit recursive function definitions is unusual.
adamc@33:
adamc@33: For Coq, however, this would be a disaster. The possibility of writing such a function would destroy all our confidence that proving a theorem means anything. Since Coq combines programs and proofs in one language, we would be able to prove every theorem with an infinite loop.
adamc@33:
adamc@33: Nonetheless, the basic insight of HOAS is a very useful one, and there are ways to realize most benefits of HOAS in Coq. We will study a particular technique of this kind in the later chapters on programming language syntax and semantics. *)
adamc@34:
adamc@34:
adamc@34: (** * An Interlude on Proof Terms *)
adamc@34:
adamc@34: (** As we have emphasized a few times already, Coq proofs are actually programs, written in the same language we have been using in our examples all along. We can get a first sense of what this means by taking a look at the definitions of some of the induction principles we have used. *)
adamc@34:
adamc@34: Print unit_ind.
adamc@34: (** [[
adamc@34:
adamc@34: unit_ind =
adamc@34: fun P : unit -> Prop => unit_rect P
adamc@34: : forall P : unit -> Prop, P tt -> forall u : unit, P u
adamc@34: ]]
adamc@34:
adamc@34: We see that this induction principle is defined in terms of a more general principle, [unit_rect]. *)
adamc@34:
adamc@34: Check unit_rect.
adamc@34: (** [[
adamc@34:
adamc@34: unit_rect
adamc@34: : forall P : unit -> Type, P tt -> forall u : unit, P u
adamc@34: ]]
adamc@34:
adamc@34: [unit_rect] gives [P] type [unit -> Type] instead of [unit -> Prop]. [Type] is another universe, like [Set] and [Prop]. In fact, it is a common supertype of both. Later on, we will discuss exactly what the significances of the different universes are. For now, it is just important that we can use [Type] as a sort of meta-universe that may turn out to be either [Set] or [Prop]. We can see the symmetry inherent in the subtyping relationship by printing the definition of another principle that was generated for [unit] automatically: *)
adamc@34:
adamc@34: Print unit_rec.
adamc@34: (** [[
adamc@34:
adamc@34: unit_rec =
adamc@34: fun P : unit -> Set => unit_rect P
adamc@34: : forall P : unit -> Set, P tt -> forall u : unit, P u
adamc@34: ]]
adamc@34:
adamc@34: This is identical to the definition for [unit_ind], except that we have substituted [Set] for [Prop]. For most inductive types [T], then, we get not just induction principles [T_ind], but also recursion principles [T_rec]. We can use [T_rec] to write recursive definitions without explicit [Fixpoint] recursion. For instance, the following two definitions are equivalent: *)
adamc@34:
adamc@34: Definition always_O (u : unit) : nat :=
adamc@34: match u with
adamc@34: | tt => O
adamc@34: end.
adamc@34:
adamc@34: Definition always_O' (u : unit) : nat :=
adamc@34: unit_rec (fun _ : unit => nat) O u.
adamc@34:
adamc@34: (** Going even further down the rabbit hole, [unit_rect] itself is not even a primitive. It is a functional program that we can write manually. *)
adamc@34:
adamc@34: Print unit_rect.
adamc@34:
adamc@34: (** [[
adamc@34:
adamc@34: unit_rect =
adamc@34: fun (P : unit -> Type) (f : P tt) (u : unit) =>
adamc@34: match u as u0 return (P u0) with
adamc@34: | tt => f
adamc@34: end
adamc@34: : forall P : unit -> Type, P tt -> forall u : unit, P u
adamc@34: ]]
adamc@34:
adamc@34: The only new feature we see is an [as] clause for a [match], which is used in concert with the [return] clause that we saw in the introduction. Since the type of the [match] is dependent on the value of the object being analyzed, we must give that object a name so that we can refer to it in the [return] clause.
adamc@34:
adamc@34: To prove that [unit_rect] is nothing special, we can reimplement it manually. *)
adamc@34:
adamc@34: Definition unit_rect' (P : unit -> Type) (f : P tt) (u : unit) :=
adamc@34: match u return (P u) with
adamc@34: | tt => f
adamc@34: end.
adamc@34:
adamc@34: (** We use the handy shorthand that lets us omit an [as] annotation when matching on a variable, simply using that variable directly in the [return] clause.
adamc@34:
adamc@34: We can check the implement of [nat_rect] as well: *)
adamc@34:
adamc@34: Print nat_rect.
adamc@34: (** [[
adamc@34:
adamc@34: nat_rect =
adamc@34: fun (P : nat -> Type) (f : P O) (f0 : forall n : nat, P n -> P (S n)) =>
adamc@34: fix F (n : nat) : P n :=
adamc@34: match n as n0 return (P n0) with
adamc@34: | O => f
adamc@34: | S n0 => f0 n0 (F n0)
adamc@34: end
adamc@34: : forall P : nat -> Type,
adamc@34: P O -> (forall n : nat, P n -> P (S n)) -> forall n : nat, P n
adamc@34: ]]
adamc@34:
adamc@34: Now we have an actual recursive definition. [fix] expressions are an anonymous form of [Fixpoint], just as [fun] expressions stand for anonymous non-recursive functions. Beyond that, the syntax of [fix] mirrors that of [Fixpoint]. We can understand the definition of [nat_rect] better by reimplementing [nat_ind] using sections. *)
adamc@34:
adamc@34: Section nat_ind'.
adamc@34: (** First, we have the property of natural numbers that we aim to prove. *)
adamc@34: Variable P : nat -> Prop.
adamc@34:
adamc@34: (** Then we require a proof of the [O] case. *)
adamc@38: Hypothesis O_case : P O.
adamc@34:
adamc@34: (** Next is a proof of the [S] case, which may assume an inductive hypothesis. *)
adamc@38: Hypothesis S_case : forall n : nat, P n -> P (S n).
adamc@34:
adamc@34: (** Finally, we define a recursive function to tie the pieces together. *)
adamc@34: Fixpoint nat_ind' (n : nat) : P n :=
adamc@34: match n return (P n) with
adamc@34: | O => O_case
adamc@34: | S n' => S_case (nat_ind' n')
adamc@34: end.
adamc@34: End nat_ind'.
adamc@34:
adamc@38: (** Closing the section adds the [Variable]s and [Hypothesis]es as new [fun]-bound arguments to [nat_ind'], and, modulo the use of [Prop] instead of [Type], we end up with the exact same definition that was generated automatically for [nat_rect].
adamc@34:
adamc@34: %\medskip%
adamc@34:
adamc@34: We can also examine the definition of [even_list_mut], which we generated with [Scheme] for a mutually-recursive type. *)
adamc@34:
adamc@34: Print even_list_mut.
adamc@34: (** [[
adamc@34:
adamc@34: even_list_mut =
adamc@34: fun (P : even_list -> Prop) (P0 : odd_list -> Prop)
adamc@34: (f : P ENil) (f0 : forall (n : nat) (o : odd_list), P0 o -> P (ECons n o))
adamc@34: (f1 : forall (n : nat) (e : even_list), P e -> P0 (OCons n e)) =>
adamc@34: fix F (e : even_list) : P e :=
adamc@34: match e as e0 return (P e0) with
adamc@34: | ENil => f
adamc@34: | ECons n o => f0 n o (F0 o)
adamc@34: end
adamc@34: with F0 (o : odd_list) : P0 o :=
adamc@34: match o as o0 return (P0 o0) with
adamc@34: | OCons n e => f1 n e (F e)
adamc@34: end
adamc@34: for F
adamc@34: : forall (P : even_list -> Prop) (P0 : odd_list -> Prop),
adamc@34: P ENil ->
adamc@34: (forall (n : nat) (o : odd_list), P0 o -> P (ECons n o)) ->
adamc@34: (forall (n : nat) (e : even_list), P e -> P0 (OCons n e)) ->
adamc@34: forall e : even_list, P e
adamc@34: ]]
adamc@34:
adamc@34: We see a mutually-recursive [fix], with the different functions separated by [with] in the same way that they would be separated by [and] in ML. A final [for] clause identifies which of the mutually-recursive functions should be the final value of the [fix] expression. Using this definition as a template, we can reimplement [even_list_mut] directly. *)
adamc@34:
adamc@34: Section even_list_mut'.
adamc@34: (** First, we need the properties that we are proving. *)
adamc@34: Variable Peven : even_list -> Prop.
adamc@34: Variable Podd : odd_list -> Prop.
adamc@34:
adamc@34: (** Next, we need proofs of the three cases. *)
adamc@38: Hypothesis ENil_case : Peven ENil.
adamc@38: Hypothesis ECons_case : forall (n : nat) (o : odd_list), Podd o -> Peven (ECons n o).
adamc@38: Hypothesis OCons_case : forall (n : nat) (e : even_list), Peven e -> Podd (OCons n e).
adamc@34:
adamc@34: (** Finally, we define the recursive functions. *)
adamc@34: Fixpoint even_list_mut' (e : even_list) : Peven e :=
adamc@34: match e return (Peven e) with
adamc@34: | ENil => ENil_case
adamc@34: | ECons n o => ECons_case n (odd_list_mut' o)
adamc@34: end
adamc@34: with odd_list_mut' (o : odd_list) : Podd o :=
adamc@34: match o return (Podd o) with
adamc@34: | OCons n e => OCons_case n (even_list_mut' e)
adamc@34: end.
adamc@34: End even_list_mut'.
adamc@34:
adamc@34: (** Even induction principles for reflexive types are easy to implement directly. For our [formula] type, we can use a recursive definition much like those we wrote above. *)
adamc@34:
adamc@34: Section formula_ind'.
adamc@34: Variable P : formula -> Prop.
adamc@38: Hypothesis Eq_case : forall n1 n2 : nat, P (Eq n1 n2).
adamc@38: Hypothesis And_case : forall f1 f2 : formula,
adamc@34: P f1 -> P f2 -> P (And f1 f2).
adamc@38: Hypothesis Forall_case : forall f : nat -> formula,
adamc@34: (forall n : nat, P (f n)) -> P (Forall f).
adamc@34:
adamc@34: Fixpoint formula_ind' (f : formula) : P f :=
adamc@34: match f return (P f) with
adamc@34: | Eq n1 n2 => Eq_case n1 n2
adamc@34: | And f1 f2 => And_case (formula_ind' f1) (formula_ind' f2)
adamc@34: | Forall f' => Forall_case f' (fun n => formula_ind' (f' n))
adamc@34: end.
adamc@34: End formula_ind'.
adamc@34:
adamc@35:
adamc@35: (** * Nested Inductive Types *)
adamc@35:
adamc@35: (** Suppose we want to extend our earlier type of binary trees to trees with arbitrary finite branching. We can use lists to give a simple definition. *)
adamc@35:
adamc@35: Inductive nat_tree : Set :=
adamc@35: | NLeaf' : nat_tree
adamc@35: | NNode' : nat -> list nat_tree -> nat_tree.
adamc@35:
adamc@35: (** This is an example of a %\textit{%##nested##%}% inductive type definition, because we use the type we are defining as an argument to a parametrized type family. Coq will not allow all such definitions; it effectively pretends that we are defining [nat_tree] mutually with a version of [list] specialized to [nat_tree], checking that the resulting expanded definition satisfies the usual rules. For instance, if we replaced [list] with a type family that used its parameter as a function argument, then the definition would be rejected as violating the positivity restriction.
adamc@35:
adamc@35: Like we encountered for mutual inductive types, we find that the automatically-generated induction principle for [nat_tree] is too weak. *)
adamc@35:
adamc@35: Check nat_tree_ind.
adamc@35: (** [[
adamc@35:
adamc@35: nat_tree_ind
adamc@35: : forall P : nat_tree -> Prop,
adamc@35: P NLeaf' ->
adamc@35: (forall (n : nat) (l : list nat_tree), P (NNode' n l)) ->
adamc@35: forall n : nat_tree, P n
adamc@35: ]]
adamc@35:
adamc@35: There is no command like [Scheme] that will implement an improved principle for us. In general, it takes creativity to figure out how to incorporate nested uses to different type families. Now that we know how to implement induction principles manually, we are in a position to apply just such creativity to this problem.
adamc@35:
adamc@35: First, we will need an auxiliary definition, characterizing what it means for a property to hold of every element of a list. *)
adamc@35:
adamc@35: Section All.
adamc@35: Variable T : Set.
adamc@35: Variable P : T -> Prop.
adamc@35:
adamc@35: Fixpoint All (ls : list T) : Prop :=
adamc@35: match ls with
adamc@35: | Nil => True
adamc@35: | Cons h t => P h /\ All t
adamc@35: end.
adamc@35: End All.
adamc@35:
adamc@35: (** It will be useful to look at the definitions of [True] and [/\], since we will want to write manual proofs of them below. *)
adamc@35:
adamc@35: Print True.
adamc@35: (** [[
adamc@35:
adamc@35: Inductive True : Prop := I : True
adamc@35: ]]
adamc@35:
adamc@35: That is, [True] is a proposition with exactly one proof, [I], which we may always supply trivially.
adamc@35:
adamc@35: Finding the definition of [/\] takes a little more work. Coq supports user registration of arbitrary parsing rules, and it is such a rule that is letting us write [/\] instead of an application of some inductive type family. We can find the underlying inductive type with the [Locate] command. *)
adamc@35:
adamc@35: Locate "/\".
adamc@35: (** [[
adamc@35:
adamc@35: Notation Scope
adamc@35: "A /\ B" := and A B : type_scope
adamc@35: (default interpretation)
adamc@35: ]] *)
adamc@35:
adamc@35: Print and.
adamc@35: (** [[
adamc@35:
adamc@35: Inductive and (A : Prop) (B : Prop) : Prop := conj : A -> B -> A /\ B
adamc@35: For conj: Arguments A, B are implicit
adamc@35: For and: Argument scopes are [type_scope type_scope]
adamc@35: For conj: Argument scopes are [type_scope type_scope _ _]
adamc@35: ]]
adamc@35:
adamc@35: In addition to the definition of [and] itself, we get information on implicit arguments and parsing rules for [and] and its constructor [conj]. We will ignore the parsing information for now. The implicit argument information tells us that we build a proof of a conjunction by calling the constructor [conj] on proofs of the conjuncts, with no need to include the types of those proofs as explicit arguments.
adamc@35:
adamc@35: %\medskip%
adamc@35:
adamc@35: Now we create a section for our induction principle, following the same basic plan as in the last section of this chapter. *)
adamc@35:
adamc@35: Section nat_tree_ind'.
adamc@35: Variable P : nat_tree -> Prop.
adamc@35:
adamc@38: Hypothesis NLeaf'_case : P NLeaf'.
adamc@38: Hypothesis NNode'_case : forall (n : nat) (ls : list nat_tree),
adamc@35: All P ls -> P (NNode' n ls).
adamc@35:
adamc@35: (** A first attempt at writing the induction principle itself follows the intuition that nested inductive type definitions are expanded into mutual inductive definitions.
adamc@35:
adamc@35: [[
adamc@35:
adamc@35: Fixpoint nat_tree_ind' (tr : nat_tree) : P tr :=
adamc@35: match tr return (P tr) with
adamc@35: | NLeaf' => NLeaf'_case
adamc@35: | NNode' n ls => NNode'_case n ls (list_nat_tree_ind ls)
adamc@35: end
adamc@35:
adamc@35: with list_nat_tree_ind (ls : list nat_tree) : All P ls :=
adamc@35: match ls return (All P ls) with
adamc@35: | Nil => I
adamc@35: | Cons tr rest => conj (nat_tree_ind' tr) (list_nat_tree_ind rest)
adamc@35: end.
adamc@35:
adamc@35: Coq rejects this definition, saying "Recursive call to nat_tree_ind' has principal argument equal to "tr" instead of rest." The term "nested inductive type" hints at the solution to the problem. Just like true mutually-inductive types require mutually-recursive induction principles, nested types require nested recursion. *)
adamc@35:
adamc@35: Fixpoint nat_tree_ind' (tr : nat_tree) : P tr :=
adamc@35: match tr return (P tr) with
adamc@35: | NLeaf' => NLeaf'_case
adamc@35: | NNode' n ls => NNode'_case n ls
adamc@35: ((fix list_nat_tree_ind (ls : list nat_tree) : All P ls :=
adamc@35: match ls return (All P ls) with
adamc@35: | Nil => I
adamc@35: | Cons tr rest => conj (nat_tree_ind' tr) (list_nat_tree_ind rest)
adamc@35: end) ls)
adamc@35: end.
adamc@35:
adamc@35: (** We include an anonymous [fix] version of [list_nat_tree_ind] that is literally %\textit{%##nested##%}% inside the definition of the recursive function corresponding to the inductive definition that had the nested use of [list]. *)
adamc@35:
adamc@35: End nat_tree_ind'.
adamc@35:
adamc@35: (** We can try our induction principle out by defining some recursive functions on [nat_tree]s and proving a theorem about them. First, we define some helper functions that operate on lists. *)
adamc@35:
adamc@35: Section map.
adamc@35: Variables T T' : Set.
adamc@35: Variable f : T -> T'.
adamc@35:
adamc@35: Fixpoint map (ls : list T) : list T' :=
adamc@35: match ls with
adamc@35: | Nil => Nil
adamc@35: | Cons h t => Cons (f h) (map t)
adamc@35: end.
adamc@35: End map.
adamc@35:
adamc@35: Fixpoint sum (ls : list nat) : nat :=
adamc@35: match ls with
adamc@35: | Nil => O
adamc@35: | Cons h t => plus h (sum t)
adamc@35: end.
adamc@35:
adamc@35: (** Now we can define a size function over our trees. *)
adamc@35:
adamc@35: Fixpoint ntsize (tr : nat_tree) : nat :=
adamc@35: match tr with
adamc@35: | NLeaf' => S O
adamc@35: | NNode' _ trs => S (sum (map ntsize trs))
adamc@35: end.
adamc@35:
adamc@35: (** Notice that Coq was smart enough to expand the definition of [map] to verify that we are using proper nested recursion, even through a use of a higher-order function. *)
adamc@35:
adamc@35: Fixpoint ntsplice (tr1 tr2 : nat_tree) {struct tr1} : nat_tree :=
adamc@35: match tr1 with
adamc@35: | NLeaf' => NNode' O (Cons tr2 Nil)
adamc@35: | NNode' n Nil => NNode' n (Cons tr2 Nil)
adamc@35: | NNode' n (Cons tr trs) => NNode' n (Cons (ntsplice tr tr2) trs)
adamc@35: end.
adamc@35:
adamc@35: (** We have defined another arbitrary notion of tree splicing, similar to before, and we can prove an analogous theorem about its relationship with tree size. We start with a useful lemma about addition. *)
adamc@35:
adamc@41: (* begin thide *)
adamc@35: Lemma plus_S : forall n1 n2 : nat,
adamc@35: plus n1 (S n2) = S (plus n1 n2).
adamc@35: induction n1; crush.
adamc@35: Qed.
adamc@41: (* end thide *)
adamc@35:
adamc@35: (** Now we begin the proof of the theorem, adding the lemma [plus_S] as a hint. *)
adamc@35:
adamc@35: Theorem ntsize_ntsplice : forall tr1 tr2 : nat_tree, ntsize (ntsplice tr1 tr2)
adamc@35: = plus (ntsize tr2) (ntsize tr1).
adamc@41: (* begin thide *)
adamc@35: Hint Rewrite plus_S : cpdt.
adamc@35:
adamc@35: (** We know that the standard induction principle is insufficient for the task, so we need to provide a [using] clause for the [induction] tactic to specify our alternate principle. *)
adamc@35: induction tr1 using nat_tree_ind'; crush.
adamc@35:
adamc@35: (** One subgoal remains: [[
adamc@35:
adamc@35: n : nat
adamc@35: ls : list nat_tree
adamc@35: H : All
adamc@35: (fun tr1 : nat_tree =>
adamc@35: forall tr2 : nat_tree,
adamc@35: ntsize (ntsplice tr1 tr2) = plus (ntsize tr2) (ntsize tr1)) ls
adamc@35: tr2 : nat_tree
adamc@35: ============================
adamc@35: ntsize
adamc@35: match ls with
adamc@35: | Nil => NNode' n (Cons tr2 Nil)
adamc@35: | Cons tr trs => NNode' n (Cons (ntsplice tr tr2) trs)
adamc@35: end = S (plus (ntsize tr2) (sum (map ntsize ls)))
adamc@35: ]]
adamc@35:
adamc@35: After a few moments of squinting at this goal, it becomes apparent that we need to do a case analysis on the structure of [ls]. The rest is routine. *)
adamc@35:
adamc@35: destruct ls; crush.
adamc@35:
adamc@36: (** We can go further in automating the proof by exploiting the hint mechanism. *)
adamc@35:
adamc@35: Restart.
adamc@35: Hint Extern 1 (ntsize (match ?LS with Nil => _ | Cons _ _ => _ end) = _) =>
adamc@35: destruct LS; crush.
adamc@35: induction tr1 using nat_tree_ind'; crush.
adamc@35: Qed.
adamc@41: (* end thide *)
adamc@35:
adamc@35: (** We will go into great detail on hints in a later chapter, but the only important thing to note here is that we register a pattern that describes a conclusion we expect to encounter during the proof. The pattern may contain unification variables, whose names are prefixed with question marks, and we may refer to those bound variables in a tactic that we ask to have run whenever the pattern matches.
adamc@35:
adamc@40: The advantage of using the hint is not very clear here, because the original proof was so short. However, the hint has fundamentally improved the readability of our proof. Before, the proof referred to the local variable [ls], which has an automatically-generated name. To a human reading the proof script without stepping through it interactively, it was not clear where [ls] came from. The hint explains to the reader the process for choosing which variables to case analyze on, and the hint can continue working even if the rest of the proof structure changes significantly. *)
adamc@36:
adamc@36:
adamc@36: (** * Manual Proofs About Constructors *)
adamc@36:
adamc@36: (** It can be useful to understand how tactics like [discriminate] and [injection] work, so it is worth stepping through a manual proof of each kind. We will start with a proof fit for [discriminate]. *)
adamc@36:
adamc@36: Theorem true_neq_false : true <> false.
adamc@41: (* begin thide *)
adamc@36: (** We begin with the tactic [red], which is short for "one step of reduction," to unfold the definition of logical negation. *)
adamc@36:
adamc@36: red.
adamc@36: (** [[
adamc@36:
adamc@36: ============================
adamc@36: true = false -> False
adamc@36: ]]
adamc@36:
adamc@36: The negation is replaced with an implication of falsehood. We use the tactic [intro H] to change the assumption of the implication into a hypothesis named [H]. *)
adamc@36:
adamc@36: intro H.
adamc@36: (** [[
adamc@36:
adamc@36: H : true = false
adamc@36: ============================
adamc@36: False
adamc@36: ]]
adamc@36:
adamc@36: This is the point in the proof where we apply some creativity. We define a function whose utility will become clear soon. *)
adamc@36:
adamc@36: Definition f (b : bool) := if b then True else False.
adamc@36:
adamc@36: (** It is worth recalling the difference between the lowercase and uppercase versions of truth and falsehood: [True] and [False] are logical propositions, while [true] and [false] are boolean values that we can case-analyze. We have defined [f] such that our conclusion of [False] is computationally equivalent to [f false]. Thus, the [change] tactic will let us change the conclusion to [f false]. *)
adamc@36:
adamc@36: change (f false).
adamc@36: (** [[
adamc@36:
adamc@36: H : true = false
adamc@36: ============================
adamc@36: f false
adamc@36: ]]
adamc@36:
adamc@36: Now the righthand side of [H]'s equality appears in the conclusion, so we can rewrite. *)
adamc@36:
adamc@36: rewrite <- H.
adamc@36: (** [[
adamc@36:
adamc@36: H : true = false
adamc@36: ============================
adamc@36: f true
adamc@36: ]]
adamc@36:
adamc@36: We are almost done. Just how close we are to done is revealed by computational simplification. *)
adamc@36:
adamc@36: simpl.
adamc@36: (** [[
adamc@36:
adamc@36: H : true = false
adamc@36: ============================
adamc@36: True
adamc@36: ]] *)
adamc@36:
adamc@36: trivial.
adamc@36: Qed.
adamc@41: (* end thide *)
adamc@36:
adamc@36: (** I have no trivial automated version of this proof to suggest, beyond using [discriminate] or [congruence] in the first place.
adamc@36:
adamc@36: %\medskip%
adamc@36:
adamc@36: We can perform a similar manual proof of injectivity of the constructor [S]. I leave a walk-through of the details to curious readers who want to run the proof script interactively. *)
adamc@36:
adamc@36: Theorem S_inj' : forall n m : nat, S n = S m -> n = m.
adamc@41: (* begin thide *)
adamc@36: intros n m H.
adamc@36: change (pred (S n) = pred (S m)).
adamc@36: rewrite H.
adamc@36: reflexivity.
adamc@36: Qed.
adamc@41: (* end thide *)
adamc@36:
adamc@37:
adamc@37: (** * Exercises *)
adamc@37:
adamc@37: (** %\begin{enumerate}%##
adamc@37:
adamc@37: %\item%#- # Define an inductive type [truth] with three constructors, [Yes], [No], and [Maybe]. [Yes] stands for certain truth, [False] for certain falsehood, and [Maybe] for an unknown situation. Define "not," "and," and "or" for this replacement boolean algebra. Prove that your implementation of "and" is commutative and distributes over your implementation of "or."#
#
adamc@37:
adamc@39: %\item%#- # Modify the first example language of Chapter 2 to include variables, where variables are represented with [nat]. Extend the syntax and semantics of expressions to accommodate the change. Your new [expDenote] function should take as a new extra first argument a value of type [var -> nat], where [var] is a synonym for naturals-as-variables, and the function assigns a value to each variable. Define a constant folding function which does a bottom-up pass over an expression, at each stage replacing every binary operation on constants with an equivalent constant. Prove that constant folding preserves the meanings of expressions.#
#
adamc@38:
adamc@39: %\item%#- # Reimplement the second example language of Chapter 2 to use mutually-inductive types instead of dependent types. That is, define two separate (non-dependent) inductive types [nat_exp] and [bool_exp] for expressions of the two different types, rather than a single indexed type. To keep things simple, you may consider only the binary operators that take naturals as operands. Add natural number variables to the language, as in the last exercise, and add an "if" expression form taking as arguments one boolean expression and two natural number expressions. Define semantics and constant-folding functions for this new language. Your constant folding should simplify not just binary operations (returning naturals or booleans) with known arguments, but also "if" expressions with known values for their test expressions but possibly undetermined "then" and "else" cases. Prove that constant-folding a natural number expression preserves its meaning.#
#
adamc@38:
adamc@38: %\item%#- # Using a reflexive inductive definition, define a type [nat_tree] of infinitary trees, with natural numbers at their leaves and a countable infinity of new trees branching out of each internal node. Define a function [increment] that increments the number in every leaf of a [nat_tree]. Define a function [leapfrog] over a natural [i] and a tree [nt]. [leapfrog] should recurse into the [i]th child of [nt], the [i+1]st child of that node, the [i+2]nd child of the next node, and so on, until reaching a leaf, in which case [leapfrog] should return the number at that leaf. Prove that the result of any call to [leapfrog] is incremented by one by calling [increment] on the tree.#
#
adamc@38:
adamc@38: %\item%#- # Define a type of trees of trees of trees of (repeat to infinity). That is, define an inductive type [trexp], whose members are either base cases containing natural numbers or binary trees of [trexp]s. Base your definition on a parameterized binary tree type [btree] that you will also define, so that [trexp] is defined as a nested inductive type. Define a function [total] that sums all of the naturals at the leaves of a [trexp]. Define a function [increment] that increments every leaf of a [trexp] by one. Prove that, for all [tr], [total (increment tr) >= total tr]. On the way to finishing this proof, you will probably want to prove a lemma and add it as a hint using the syntax [Hint Resolve name_of_lemma.].#
#
adamc@38:
adamc@38: %\item%#- # Prove discrimination and injectivity theorems for the [nat_btree] type defined earlier in this chapter. In particular, without using the tactics [discriminate], [injection], or [congruence], prove that no leaf equals any node, and prove that two equal nodes carry the same natural number.#
#
adamc@37:
adamc@37: #
#%\end{enumerate}% *)