Commit ae07f650 authored by Adam Chlipala's avatar Adam Chlipala

Break into Parts

parent 28f1bb13
...@@ -16,7 +16,9 @@ Set Implicit Arguments. ...@@ -16,7 +16,9 @@ Set Implicit Arguments.
(* end hide *) (* end hide *)
(** %\chapter{Introducing Inductive Types}% *) (** %\part{Basic Programming and Proving}
\chapter{Introducing Inductive Types}% *)
(** 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. *) (** 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. *)
......
...@@ -16,7 +16,9 @@ Set Implicit Arguments. ...@@ -16,7 +16,9 @@ Set Implicit Arguments.
(* end hide *) (* end hide *)
(** %\chapter{Subset Types and Variations}% *) (** %\part{Programming with Dependent Types}
\chapter{Subset Types and Variations}% *)
(** So far, we have seen many examples of what we might call "classical program verification." We write programs, write their specifications, and then prove that the programs satisfy their specifications. The programs that we have written in Coq have been normal functional programs that we could just as well have written in Haskell or ML. In this chapter, we start investigating uses of %\textit{%#<i>#dependent types#</i>#%}% to integrate programming, specification, and proving into a single phase. *) (** So far, we have seen many examples of what we might call "classical program verification." We write programs, write their specifications, and then prove that the programs satisfy their specifications. The programs that we have written in Coq have been normal functional programs that we could just as well have written in Haskell or ML. In this chapter, we start investigating uses of %\textit{%#<i>#dependent types#</i>#%}% to integrate programming, specification, and proving into a single phase. *)
...@@ -569,10 +571,6 @@ Eval simpl in typeCheck (Nat 0). ...@@ -569,10 +571,6 @@ Eval simpl in typeCheck (Nat 0).
Eval simpl in typeCheck (Plus (Nat 1) (Nat 2)). Eval simpl in typeCheck (Plus (Nat 1) (Nat 2)).
Eval simpl in typeCheck (Plus (Nat 1) (Bool false)). Eval simpl in typeCheck (Plus (Nat 1) (Bool false)).
Print sumor.
Notation "e1 ;;; e2" := (if e1 then e2 else !!) Notation "e1 ;;; e2" := (if e1 then e2 else !!)
(right associativity, at level 60). (right associativity, at level 60).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment