File: introduction.rst

package info (click to toggle)
coq-doc 8.16.1-1
  • links: PTS, VCS
  • area: non-free
  • in suites: bookworm
  • size: 42,788 kB
  • sloc: ml: 219,673; sh: 4,035; python: 3,372; ansic: 2,529; makefile: 728; lisp: 279; javascript: 87; xml: 24; sed: 2
file content (68 lines) | stat: -rw-r--r-- 3,523 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
This is the reference manual of Coq.  Coq is an interactive theorem
prover.  It lets you formalize mathematical concepts and then helps
you interactively generate machine-checked proofs of theorems.
Machine checking gives users much more confidence that the proofs are
correct compared to human-generated and -checked proofs.  Coq has been
used in a number of flagship verification projects, including the
`CompCert verified C compiler <http://compcert.inria.fr/>`_, and has
served to verify the proof of the `four color theorem
<https://github.com/math-comp/fourcolor>`_ (among many other
mathematical formalizations).

Users generate proofs by entering a series of tactics that constitute
steps in the proof.  There are many built-in tactics, some of which
are elementary, while others implement complex decision procedures
(such as :tacn:`lia`, a decision procedure for linear integer
arithmetic).  :ref:`Ltac <ltac>` and its planned replacement,
:ref:`Ltac2 <ltac2>`, provide languages to define new tactics by
combining existing tactics with looping and conditional constructs.
These permit automation of large parts of proofs and sometimes entire
proofs.  Furthermore, users can add novel tactics or functionality by
creating Coq plugins using OCaml.

The Coq kernel, a small part of Coq, does the final verification that
the tactic-generated proof is valid.  Usually the tactic-generated
proof is indeed correct, but delegating proof verification to the
kernel means that even if a tactic is buggy, it won't be able to
introduce an incorrect proof into the system.

Finally, Coq also supports extraction of verified programs to
programming languages such as OCaml and Haskell.  This provides a way
of executing Coq code efficiently and can be used to create verified
software libraries.

To learn Coq, beginners are advised to first start with a tutorial /
book.  Several such tutorials / books are listed at
https://coq.inria.fr/documentation.

This manual is organized in three main parts, plus an appendix:

- **The first part presents the specification language of Coq**, that
  allows to define programs and state mathematical theorems.
  :ref:`core-language` presents the language that the kernel of Coq
  understands.  :ref:`extensions` presents the richer language, with
  notations, implicits, etc. that a user can use and which is
  translated down to the language of the kernel by means of an
  "elaboration process".

- **The second part presents proof mode**, the central
  feature of Coq.  :ref:`writing-proofs` introduces this interactive
  mode and the available proof languages.
  :ref:`automatic-tactics` presents some more advanced tactics, while
  :ref:`writing-tactics` is about the languages that allow a user to
  combine tactics together and develop new ones.

- **The third part shows how to use Coq in practice.**
  :ref:`libraries` presents some of the essential reusable blocks from
  the ecosystem and some particularly important extensions such as the
  program extraction mechanism.  :ref:`tools` documents important
  tools that a user needs to build a Coq project.

- In the appendix, :ref:`history-and-changes` presents the history of
  Coq and changes in recent releases.  This is an important reference
  if you upgrade the version of Coq that you use.  The various
  :ref:`indexes <indexes>` are very useful to **quickly browse the
  manual and find what you are looking for.** They are often the main
  entry point to the manual.

The full table of contents is presented below: