doc-src/Nitpick/nitpick.tex
author blanchet
Thu Dec 17 15:22:11 2009 +0100 (2009-12-17)
changeset 34124 c4628a1dcf75
parent 34038 a2736debeabd
child 34126 8a2c5d7aff51
permissions -rw-r--r--
added support for binary nat/int representation to Nitpick
blanchet@33191
     1
\documentclass[a4paper,12pt]{article}
blanchet@33191
     2
\usepackage[T1]{fontenc}
blanchet@33191
     3
\usepackage{amsmath}
blanchet@33191
     4
\usepackage{amssymb}
blanchet@33564
     5
\usepackage[english,french]{babel}
blanchet@33191
     6
\usepackage{color}
blanchet@33191
     7
\usepackage{graphicx}
blanchet@33191
     8
%\usepackage{mathpazo}
blanchet@33191
     9
\usepackage{multicol}
blanchet@33191
    10
\usepackage{stmaryrd}
blanchet@33191
    11
%\usepackage[scaled=.85]{beramono}
blanchet@33191
    12
\usepackage{../iman,../pdfsetup}
blanchet@33191
    13
blanchet@33191
    14
%\oddsidemargin=4.6mm
blanchet@33191
    15
%\evensidemargin=4.6mm
blanchet@33191
    16
%\textwidth=150mm
blanchet@33191
    17
%\topmargin=4.6mm
blanchet@33191
    18
%\headheight=0mm
blanchet@33191
    19
%\headsep=0mm
blanchet@33191
    20
%\textheight=234mm
blanchet@33191
    21
blanchet@33191
    22
\def\Colon{\mathord{:\mkern-1.5mu:}}
blanchet@33191
    23
%\def\lbrakk{\mathopen{\lbrack\mkern-3.25mu\lbrack}}
blanchet@33191
    24
%\def\rbrakk{\mathclose{\rbrack\mkern-3.255mu\rbrack}}
blanchet@33191
    25
\def\lparr{\mathopen{(\mkern-4mu\mid}}
blanchet@33191
    26
\def\rparr{\mathclose{\mid\mkern-4mu)}}
blanchet@33191
    27
blanchet@33191
    28
\def\undef{\textit{undefined}}
blanchet@33191
    29
\def\unk{{?}}
blanchet@33191
    30
%\def\unr{\textit{others}}
blanchet@33191
    31
\def\unr{\ldots}
blanchet@33191
    32
\def\Abs#1{\hbox{\rm{\flqq}}{\,#1\,}\hbox{\rm{\frqq}}}
blanchet@33191
    33
\def\Q{{\smash{\lower.2ex\hbox{$\scriptstyle?$}}}}
blanchet@33191
    34
blanchet@33191
    35
\hyphenation{Mini-Sat size-change First-Steps grand-parent nit-pick
blanchet@33191
    36
counter-example counter-examples data-type data-types co-data-type 
blanchet@33191
    37
co-data-types in-duc-tive co-in-duc-tive}
blanchet@33191
    38
blanchet@33191
    39
\urlstyle{tt}
blanchet@33191
    40
blanchet@33191
    41
\begin{document}
blanchet@33191
    42
blanchet@33564
    43
\selectlanguage{english}
blanchet@33564
    44
blanchet@33191
    45
\title{\includegraphics[scale=0.5]{isabelle_nitpick} \\[4ex]
blanchet@33191
    46
Picking Nits \\[\smallskipamount]
blanchet@33887
    47
\Large A User's Guide to Nitpick for Isabelle/HOL}
blanchet@33191
    48
\author{\hbox{} \\
blanchet@33191
    49
Jasmin Christian Blanchette \\
blanchet@33887
    50
{\normalsize Institut f\"ur Informatik, Technische Universit\"at M\"unchen} \\
blanchet@33191
    51
\hbox{}}
blanchet@33191
    52
blanchet@33191
    53
\maketitle
blanchet@33191
    54
blanchet@33191
    55
\tableofcontents
blanchet@33191
    56
blanchet@33191
    57
\setlength{\parskip}{.7em plus .2em minus .1em}
blanchet@33191
    58
\setlength{\parindent}{0pt}
blanchet@33191
    59
\setlength{\abovedisplayskip}{\parskip}
blanchet@33191
    60
\setlength{\abovedisplayshortskip}{.9\parskip}
blanchet@33191
    61
\setlength{\belowdisplayskip}{\parskip}
blanchet@33191
    62
\setlength{\belowdisplayshortskip}{.9\parskip}
blanchet@33191
    63
blanchet@33191
    64
% General-purpose enum environment with correct spacing
blanchet@33191
    65
\newenvironment{enum}%
blanchet@33191
    66
    {\begin{list}{}{%
blanchet@33191
    67
        \setlength{\topsep}{.1\parskip}%
blanchet@33191
    68
        \setlength{\partopsep}{.1\parskip}%
blanchet@33191
    69
        \setlength{\itemsep}{\parskip}%
blanchet@33191
    70
        \advance\itemsep by-\parsep}}
blanchet@33191
    71
    {\end{list}}
blanchet@33191
    72
blanchet@33191
    73
\def\pre{\begingroup\vskip0pt plus1ex\advance\leftskip by\leftmargin
blanchet@33191
    74
\advance\rightskip by\leftmargin}
blanchet@33191
    75
\def\post{\vskip0pt plus1ex\endgroup}
blanchet@33191
    76
blanchet@33191
    77
\def\prew{\pre\advance\rightskip by-\leftmargin}
blanchet@33191
    78
\def\postw{\post}
blanchet@33191
    79
blanchet@33191
    80
\section{Introduction}
blanchet@33191
    81
\label{introduction}
blanchet@33191
    82
blanchet@33191
    83
Nitpick \cite{blanchette-nipkow-2009} is a counterexample generator for
blanchet@33191
    84
Isabelle/HOL \cite{isa-tutorial} that is designed to handle formulas
blanchet@33191
    85
combining (co)in\-duc\-tive datatypes, (co)in\-duc\-tively defined predicates, and
blanchet@33191
    86
quantifiers. It builds on Kodkod \cite{torlak-jackson-2007}, a highly optimized
blanchet@33191
    87
first-order relational model finder developed by the Software Design Group at
blanchet@33191
    88
MIT. It is conceptually similar to Refute \cite{weber-2008}, from which it
blanchet@33191
    89
borrows many ideas and code fragments, but it benefits from Kodkod's
blanchet@33191
    90
optimizations and a new encoding scheme. The name Nitpick is shamelessly
blanchet@33191
    91
appropriated from a now retired Alloy precursor.
blanchet@33191
    92
blanchet@33191
    93
Nitpick is easy to use---you simply enter \textbf{nitpick} after a putative
blanchet@33191
    94
theorem and wait a few seconds. Nonetheless, there are situations where knowing
blanchet@33191
    95
how it works under the hood and how it reacts to various options helps
blanchet@33191
    96
increase the test coverage. This manual also explains how to install the tool on
blanchet@33191
    97
your workstation. Should the motivation fail you, think of the many hours of
blanchet@33191
    98
hard work Nitpick will save you. Proving non-theorems is \textsl{hard work}.
blanchet@33191
    99
blanchet@33191
   100
Another common use of Nitpick is to find out whether the axioms of a locale are
blanchet@33191
   101
satisfiable, while the locale is being developed. To check this, it suffices to
blanchet@33191
   102
write
blanchet@33191
   103
blanchet@33191
   104
\prew
blanchet@33191
   105
\textbf{lemma}~``$\textit{False}$'' \\
blanchet@33191
   106
\textbf{nitpick}~[\textit{show\_all}]
blanchet@33191
   107
\postw
blanchet@33191
   108
blanchet@33191
   109
after the locale's \textbf{begin} keyword. To falsify \textit{False}, Nitpick
blanchet@33191
   110
must find a model for the axioms. If it finds no model, we have an indication
blanchet@33191
   111
that the axioms might be unsatisfiable.
blanchet@33191
   112
blanchet@33195
   113
Nitpick requires the Kodkodi package for Isabelle as well as a Java 1.5 virtual
blanchet@33195
   114
machine called \texttt{java}. The examples presented in this manual can be found
blanchet@33195
   115
in Isabelle's \texttt{src/HOL/Nitpick\_Examples/Manual\_Nits.thy} theory.
blanchet@33195
   116
blanchet@33561
   117
Throughout this manual, we will explicitly invoke the \textbf{nitpick} command.
blanchet@33561
   118
Nitpick also provides an automatic mode that can be enabled using the
blanchet@33561
   119
``Auto Nitpick'' option from the ``Isabelle'' menu in Proof General. In this
blanchet@33561
   120
mode, Nitpick is run on every newly entered theorem, much like Auto Quickcheck.
blanchet@33561
   121
The collective time limit for Auto Nitpick and Auto Quickcheck can be set using
blanchet@33561
   122
the ``Auto Counterexample Time Limit'' option.
blanchet@33561
   123
blanchet@33191
   124
\newbox\boxA
blanchet@33191
   125
\setbox\boxA=\hbox{\texttt{nospam}}
blanchet@33191
   126
blanchet@33191
   127
The known bugs and limitations at the time of writing are listed in
blanchet@33191
   128
\S\ref{known-bugs-and-limitations}. Comments and bug reports concerning Nitpick
blanchet@33191
   129
or this manual should be directed to
blanchet@33191
   130
\texttt{blan{\color{white}nospam}\kern-\wd\boxA{}chette@\allowbreak
blanchet@33191
   131
in.\allowbreak tum.\allowbreak de}.
blanchet@33191
   132
blanchet@33191
   133
\vskip2.5\smallskipamount
blanchet@33191
   134
blanchet@33191
   135
\textbf{Acknowledgment.} The author would like to thank Mark Summerfield for
blanchet@33191
   136
suggesting several textual improvements.
blanchet@33191
   137
% and Perry James for reporting a typo.
blanchet@33191
   138
blanchet@33191
   139
\section{First Steps}
blanchet@33191
   140
\label{first-steps}
blanchet@33191
   141
blanchet@33191
   142
This section introduces Nitpick by presenting small examples. If possible, you
blanchet@33191
   143
should try out the examples on your workstation. Your theory file should start
blanchet@33191
   144
the standard way:
blanchet@33191
   145
blanchet@33191
   146
\prew
blanchet@33191
   147
\textbf{theory}~\textit{Scratch} \\
blanchet@33191
   148
\textbf{imports}~\textit{Main} \\
blanchet@33191
   149
\textbf{begin}
blanchet@33191
   150
\postw
blanchet@33191
   151
blanchet@33191
   152
The results presented here were obtained using the JNI version of MiniSat and
blanchet@33191
   153
with multithreading disabled to reduce nondeterminism. This was done by adding
blanchet@33191
   154
the line
blanchet@33191
   155
blanchet@33191
   156
\prew
blanchet@33191
   157
\textbf{nitpick\_params} [\textit{sat\_solver}~= \textit{MiniSatJNI}, \,\textit{max\_threads}~= 1]
blanchet@33191
   158
\postw
blanchet@33191
   159
blanchet@33191
   160
after the \textbf{begin} keyword. The JNI version of MiniSat is bundled with
blanchet@33191
   161
Kodkodi and is precompiled for the major platforms. Other SAT solvers can also
blanchet@33191
   162
be installed, as explained in \S\ref{optimizations}. If you have already
blanchet@33191
   163
configured SAT solvers in Isabelle (e.g., for Refute), these will also be
blanchet@33191
   164
available to Nitpick.
blanchet@33191
   165
blanchet@33191
   166
\subsection{Propositional Logic}
blanchet@33191
   167
\label{propositional-logic}
blanchet@33191
   168
blanchet@33191
   169
Let's start with a trivial example from propositional logic:
blanchet@33191
   170
blanchet@33191
   171
\prew
blanchet@33191
   172
\textbf{lemma}~``$P \longleftrightarrow Q$'' \\
blanchet@33191
   173
\textbf{nitpick}
blanchet@33191
   174
\postw
blanchet@33191
   175
blanchet@33191
   176
You should get the following output:
blanchet@33191
   177
blanchet@33191
   178
\prew
blanchet@33191
   179
\slshape
blanchet@33191
   180
Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   181
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   182
\hbox{}\qquad\qquad $P = \textit{True}$ \\
blanchet@33191
   183
\hbox{}\qquad\qquad $Q = \textit{False}$
blanchet@33191
   184
\postw
blanchet@33191
   185
blanchet@33191
   186
Nitpick can also be invoked on individual subgoals, as in the example below:
blanchet@33191
   187
blanchet@33191
   188
\prew
blanchet@33191
   189
\textbf{apply}~\textit{auto} \\[2\smallskipamount]
blanchet@33191
   190
{\slshape goal (2 subgoals): \\
blanchet@33191
   191
\ 1. $P\,\Longrightarrow\, Q$ \\
blanchet@33191
   192
\ 2. $Q\,\Longrightarrow\, P$} \\[2\smallskipamount]
blanchet@33191
   193
\textbf{nitpick}~1 \\[2\smallskipamount]
blanchet@33191
   194
{\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   195
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   196
\hbox{}\qquad\qquad $P = \textit{True}$ \\
blanchet@33191
   197
\hbox{}\qquad\qquad $Q = \textit{False}$} \\[2\smallskipamount]
blanchet@33191
   198
\textbf{nitpick}~2 \\[2\smallskipamount]
blanchet@33191
   199
{\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   200
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   201
\hbox{}\qquad\qquad $P = \textit{False}$ \\
blanchet@33191
   202
\hbox{}\qquad\qquad $Q = \textit{True}$} \\[2\smallskipamount]
blanchet@33191
   203
\textbf{oops}
blanchet@33191
   204
\postw
blanchet@33191
   205
blanchet@33191
   206
\subsection{Type Variables}
blanchet@33191
   207
\label{type-variables}
blanchet@33191
   208
blanchet@33191
   209
If you are left unimpressed by the previous example, don't worry. The next
blanchet@33191
   210
one is more mind- and computer-boggling:
blanchet@33191
   211
blanchet@33191
   212
\prew
blanchet@33191
   213
\textbf{lemma} ``$P~x\,\Longrightarrow\, P~(\textrm{THE}~y.\;P~y)$''
blanchet@33191
   214
\postw
blanchet@33191
   215
\pagebreak[2] %% TYPESETTING
blanchet@33191
   216
blanchet@33191
   217
The putative lemma involves the definite description operator, {THE}, presented
blanchet@33191
   218
in section 5.10.1 of the Isabelle tutorial \cite{isa-tutorial}. The
blanchet@33191
   219
operator is defined by the axiom $(\textrm{THE}~x.\; x = a) = a$. The putative
blanchet@33191
   220
lemma is merely asserting the indefinite description operator axiom with {THE}
blanchet@33191
   221
substituted for {SOME}.
blanchet@33191
   222
blanchet@33191
   223
The free variable $x$ and the bound variable $y$ have type $'a$. For formulas
blanchet@33191
   224
containing type variables, Nitpick enumerates the possible domains for each type
blanchet@33191
   225
variable, up to a given cardinality (8 by default), looking for a finite
blanchet@33191
   226
countermodel:
blanchet@33191
   227
blanchet@33191
   228
\prew
blanchet@33191
   229
\textbf{nitpick} [\textit{verbose}] \\[2\smallskipamount]
blanchet@33191
   230
\slshape
blanchet@33191
   231
Trying 8 scopes: \nopagebreak \\
blanchet@33191
   232
\hbox{}\qquad \textit{card}~$'a$~= 1; \\
blanchet@33191
   233
\hbox{}\qquad \textit{card}~$'a$~= 2; \\
blanchet@33191
   234
\hbox{}\qquad $\qquad\vdots$ \\[.5\smallskipamount]
blanchet@33191
   235
\hbox{}\qquad \textit{card}~$'a$~= 8. \\[2\smallskipamount]
blanchet@33191
   236
Nitpick found a counterexample for \textit{card} $'a$~= 3: \\[2\smallskipamount]
blanchet@33191
   237
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   238
\hbox{}\qquad\qquad $P = \{a_2,\, a_3\}$ \\
blanchet@33191
   239
\hbox{}\qquad\qquad $x = a_3$ \\[2\smallskipamount]
blanchet@33191
   240
Total time: 580 ms.
blanchet@33191
   241
\postw
blanchet@33191
   242
blanchet@33191
   243
Nitpick found a counterexample in which $'a$ has cardinality 3. (For
blanchet@33191
   244
cardinalities 1 and 2, the formula holds.) In the counterexample, the three
blanchet@33191
   245
values of type $'a$ are written $a_1$, $a_2$, and $a_3$.
blanchet@33191
   246
blanchet@33191
   247
The message ``Trying $n$ scopes: {\ldots}''\ is shown only if the option
blanchet@33191
   248
\textit{verbose} is enabled. You can specify \textit{verbose} each time you
blanchet@33191
   249
invoke \textbf{nitpick}, or you can set it globally using the command
blanchet@33191
   250
blanchet@33191
   251
\prew
blanchet@33191
   252
\textbf{nitpick\_params} [\textit{verbose}]
blanchet@33191
   253
\postw
blanchet@33191
   254
blanchet@33191
   255
This command also displays the current default values for all of the options
blanchet@33191
   256
supported by Nitpick. The options are listed in \S\ref{option-reference}.
blanchet@33191
   257
blanchet@33191
   258
\subsection{Constants}
blanchet@33191
   259
\label{constants}
blanchet@33191
   260
blanchet@33191
   261
By just looking at Nitpick's output, it might not be clear why the
blanchet@33191
   262
counterexample in \S\ref{type-variables} is genuine. Let's invoke Nitpick again,
blanchet@33191
   263
this time telling it to show the values of the constants that occur in the
blanchet@33191
   264
formula:
blanchet@33191
   265
blanchet@33191
   266
\prew
blanchet@33191
   267
\textbf{lemma}~``$P~x\,\Longrightarrow\, P~(\textrm{THE}~y.\;P~y)$'' \\
blanchet@33191
   268
\textbf{nitpick}~[\textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   269
\slshape
blanchet@33191
   270
Nitpick found a counterexample for \textit{card} $'a$~= 3: \\[2\smallskipamount]
blanchet@33191
   271
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   272
\hbox{}\qquad\qquad $P = \{a_2,\, a_3\}$ \\
blanchet@33191
   273
\hbox{}\qquad\qquad $x = a_3$ \\
blanchet@33191
   274
\hbox{}\qquad Constant: \nopagebreak \\
blanchet@33191
   275
\hbox{}\qquad\qquad $\textit{The}~\textsl{fallback} = a_1$
blanchet@33191
   276
\postw
blanchet@33191
   277
blanchet@33191
   278
We can see more clearly now. Since the predicate $P$ isn't true for a unique
blanchet@33191
   279
value, $\textrm{THE}~y.\;P~y$ can denote any value of type $'a$, even
blanchet@33191
   280
$a_1$. Since $P~a_1$ is false, the entire formula is falsified.
blanchet@33191
   281
blanchet@33191
   282
As an optimization, Nitpick's preprocessor introduced the special constant
blanchet@33191
   283
``\textit{The} fallback'' corresponding to $\textrm{THE}~y.\;P~y$ (i.e.,
blanchet@33191
   284
$\mathit{The}~(\lambda y.\;P~y)$) when there doesn't exist a unique $y$
blanchet@33191
   285
satisfying $P~y$. We disable this optimization by passing the
blanchet@33191
   286
\textit{full\_descrs} option:
blanchet@33191
   287
blanchet@33191
   288
\prew
blanchet@33191
   289
\textbf{nitpick}~[\textit{full\_descrs},\, \textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   290
\slshape
blanchet@33191
   291
Nitpick found a counterexample for \textit{card} $'a$~= 3: \\[2\smallskipamount]
blanchet@33191
   292
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   293
\hbox{}\qquad\qquad $P = \{a_2,\, a_3\}$ \\
blanchet@33191
   294
\hbox{}\qquad\qquad $x = a_3$ \\
blanchet@33191
   295
\hbox{}\qquad Constant: \nopagebreak \\
blanchet@33191
   296
\hbox{}\qquad\qquad $\hbox{\slshape THE}~y.\;P~y = a_1$
blanchet@33191
   297
\postw
blanchet@33191
   298
blanchet@33191
   299
As the result of another optimization, Nitpick directly assigned a value to the
blanchet@33191
   300
subterm $\textrm{THE}~y.\;P~y$, rather than to the \textit{The} constant. If we
blanchet@33191
   301
disable this second optimization by using the command
blanchet@33191
   302
blanchet@33191
   303
\prew
blanchet@33191
   304
\textbf{nitpick}~[\textit{dont\_specialize},\, \textit{full\_descrs},\,
blanchet@33191
   305
\textit{show\_consts}]
blanchet@33191
   306
\postw
blanchet@33191
   307
blanchet@33191
   308
we finally get \textit{The}:
blanchet@33191
   309
blanchet@33191
   310
\prew
blanchet@33191
   311
\slshape Constant: \nopagebreak \\
blanchet@33191
   312
\hbox{}\qquad $\mathit{The} = \undef{}
blanchet@33191
   313
    (\!\begin{aligned}[t]%
blanchet@33191
   314
    & \{\} := a_3,\> \{a_3\} := a_3,\> \{a_2\} := a_2, \\[-2pt] %% TYPESETTING
blanchet@33191
   315
    & \{a_2, a_3\} := a_1,\> \{a_1\} := a_1,\> \{a_1, a_3\} := a_3, \\[-2pt]
blanchet@33191
   316
    & \{a_1, a_2\} := a_3,\> \{a_1, a_2, a_3\} := a_3)\end{aligned}$
blanchet@33191
   317
\postw
blanchet@33191
   318
blanchet@33191
   319
Notice that $\textit{The}~(\lambda y.\;P~y) = \textit{The}~\{a_2, a_3\} = a_1$,
blanchet@33191
   320
just like before.\footnote{The \undef{} symbol's presence is explained as
blanchet@33191
   321
follows: In higher-order logic, any function can be built from the undefined
blanchet@33191
   322
function using repeated applications of the function update operator $f(x :=
blanchet@33191
   323
y)$, just like any list can be built from the empty list using $x \mathbin{\#}
blanchet@33191
   324
xs$.}
blanchet@33191
   325
blanchet@33191
   326
Our misadventures with THE suggest adding `$\exists!x{.}$' (``there exists a
blanchet@33191
   327
unique $x$ such that'') at the front of our putative lemma's assumption:
blanchet@33191
   328
blanchet@33191
   329
\prew
blanchet@33191
   330
\textbf{lemma}~``$\exists {!}x.\; P~x\,\Longrightarrow\, P~(\textrm{THE}~y.\;P~y)$''
blanchet@33191
   331
\postw
blanchet@33191
   332
blanchet@33191
   333
The fix appears to work:
blanchet@33191
   334
blanchet@33191
   335
\prew
blanchet@33191
   336
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   337
\slshape Nitpick found no counterexample.
blanchet@33191
   338
\postw
blanchet@33191
   339
blanchet@33191
   340
We can further increase our confidence in the formula by exhausting all
blanchet@33191
   341
cardinalities up to 50:
blanchet@33191
   342
blanchet@33191
   343
\prew
blanchet@33191
   344
\textbf{nitpick} [\textit{card} $'a$~= 1--50]\footnote{The symbol `--'
blanchet@33191
   345
can be entered as \texttt{-} (hyphen) or
blanchet@33191
   346
\texttt{\char`\\\char`\<midarrow\char`\>}.} \\[2\smallskipamount]
blanchet@33191
   347
\slshape Nitpick found no counterexample.
blanchet@33191
   348
\postw
blanchet@33191
   349
blanchet@33191
   350
Let's see if Sledgehammer \cite{sledgehammer-2009} can find a proof:
blanchet@33191
   351
blanchet@33191
   352
\prew
blanchet@33191
   353
\textbf{sledgehammer} \\[2\smallskipamount]
blanchet@33191
   354
{\slshape Sledgehammer: external prover ``$e$'' for subgoal 1: \\
blanchet@33191
   355
$\exists{!}x.\; P~x\,\Longrightarrow\, P~(\hbox{\slshape THE}~y.\; P~y)$ \\
blanchet@33191
   356
Try this command: \textrm{apply}~(\textit{metis~the\_equality})} \\[2\smallskipamount]
blanchet@33191
   357
\textbf{apply}~(\textit{metis~the\_equality\/}) \nopagebreak \\[2\smallskipamount]
blanchet@33191
   358
{\slshape No subgoals!}% \\[2\smallskipamount]
blanchet@33191
   359
%\textbf{done}
blanchet@33191
   360
\postw
blanchet@33191
   361
blanchet@33191
   362
This must be our lucky day.
blanchet@33191
   363
blanchet@33191
   364
\subsection{Skolemization}
blanchet@33191
   365
\label{skolemization}
blanchet@33191
   366
blanchet@33191
   367
Are all invertible functions onto? Let's find out:
blanchet@33191
   368
blanchet@33191
   369
\prew
blanchet@33191
   370
\textbf{lemma} ``$\exists g.\; \forall x.~g~(f~x) = x
blanchet@33191
   371
 \,\Longrightarrow\, \forall y.\; \exists x.~y = f~x$'' \\
blanchet@33191
   372
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   373
\slshape
blanchet@33191
   374
Nitpick found a counterexample for \textit{card} $'a$~= 2 and \textit{card} $'b$~=~1: \\[2\smallskipamount]
blanchet@33191
   375
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   376
\hbox{}\qquad\qquad $f = \undef{}(b_1 := a_1)$ \\
blanchet@33191
   377
\hbox{}\qquad Skolem constants: \nopagebreak \\
blanchet@33191
   378
\hbox{}\qquad\qquad $g = \undef{}(a_1 := b_1,\> a_2 := b_1)$ \\
blanchet@33191
   379
\hbox{}\qquad\qquad $y = a_2$
blanchet@33191
   380
\postw
blanchet@33191
   381
blanchet@33191
   382
Although $f$ is the only free variable occurring in the formula, Nitpick also
blanchet@33191
   383
displays values for the bound variables $g$ and $y$. These values are available
blanchet@33191
   384
to Nitpick because it performs skolemization as a preprocessing step.
blanchet@33191
   385
blanchet@33191
   386
In the previous example, skolemization only affected the outermost quantifiers.
blanchet@33191
   387
This is not always the case, as illustrated below:
blanchet@33191
   388
blanchet@33191
   389
\prew
blanchet@33191
   390
\textbf{lemma} ``$\exists x.\; \forall f.\; f~x = x$'' \\
blanchet@33191
   391
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   392
\slshape
blanchet@33191
   393
Nitpick found a counterexample for \textit{card} $'a$~= 2: \\[2\smallskipamount]
blanchet@33191
   394
\hbox{}\qquad Skolem constant: \nopagebreak \\
blanchet@33191
   395
\hbox{}\qquad\qquad $\lambda x.\; f =
blanchet@33191
   396
    \undef{}(\!\begin{aligned}[t]
blanchet@33191
   397
    & a_1 := \undef{}(a_1 := a_2,\> a_2 := a_1), \\[-2pt]
blanchet@33191
   398
    & a_2 := \undef{}(a_1 := a_1,\> a_2 := a_1))\end{aligned}$
blanchet@33191
   399
\postw
blanchet@33191
   400
blanchet@33191
   401
The variable $f$ is bound within the scope of $x$; therefore, $f$ depends on
blanchet@33191
   402
$x$, as suggested by the notation $\lambda x.\,f$. If $x = a_1$, then $f$ is the
blanchet@33191
   403
function that maps $a_1$ to $a_2$ and vice versa; otherwise, $x = a_2$ and $f$
blanchet@33191
   404
maps both $a_1$ and $a_2$ to $a_1$. In both cases, $f~x \not= x$.
blanchet@33191
   405
blanchet@33191
   406
The source of the Skolem constants is sometimes more obscure:
blanchet@33191
   407
blanchet@33191
   408
\prew
blanchet@33191
   409
\textbf{lemma} ``$\mathit{refl}~r\,\Longrightarrow\, \mathit{sym}~r$'' \\
blanchet@33191
   410
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   411
\slshape
blanchet@33191
   412
Nitpick found a counterexample for \textit{card} $'a$~= 2: \\[2\smallskipamount]
blanchet@33191
   413
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   414
\hbox{}\qquad\qquad $r = \{(a_1, a_1),\, (a_2, a_1),\, (a_2, a_2)\}$ \\
blanchet@33191
   415
\hbox{}\qquad Skolem constants: \nopagebreak \\
blanchet@33191
   416
\hbox{}\qquad\qquad $\mathit{sym}.x = a_2$ \\
blanchet@33191
   417
\hbox{}\qquad\qquad $\mathit{sym}.y = a_1$
blanchet@33191
   418
\postw
blanchet@33191
   419
blanchet@33191
   420
What happened here is that Nitpick expanded the \textit{sym} constant to its
blanchet@33191
   421
definition:
blanchet@33191
   422
blanchet@33191
   423
\prew
blanchet@33191
   424
$\mathit{sym}~r \,\equiv\,
blanchet@33191
   425
 \forall x\> y.\,\> (x, y) \in r \longrightarrow (y, x) \in r.$
blanchet@33191
   426
\postw
blanchet@33191
   427
blanchet@33191
   428
As their names suggest, the Skolem constants $\mathit{sym}.x$ and
blanchet@33191
   429
$\mathit{sym}.y$ are simply the bound variables $x$ and $y$
blanchet@33191
   430
from \textit{sym}'s definition.
blanchet@33191
   431
blanchet@33191
   432
Although skolemization is a useful optimization, you can disable it by invoking
blanchet@33191
   433
Nitpick with \textit{dont\_skolemize}. See \S\ref{optimizations} for details.
blanchet@33191
   434
blanchet@33191
   435
\subsection{Natural Numbers and Integers}
blanchet@33191
   436
\label{natural-numbers-and-integers}
blanchet@33191
   437
blanchet@33191
   438
Because of the axiom of infinity, the type \textit{nat} does not admit any
blanchet@34124
   439
finite models. To deal with this, Nitpick's approach is to consider finite
blanchet@34124
   440
subsets $N$ of \textit{nat} and maps all numbers $\notin N$ to the undefined
blanchet@34124
   441
value (displayed as `$\unk$'). The type \textit{int} is handled similarly.
blanchet@34124
   442
Internally, undefined values lead to a three-valued logic.
blanchet@33191
   443
blanchet@33191
   444
Here is an example involving \textit{int}:
blanchet@33191
   445
blanchet@33191
   446
\prew
blanchet@33191
   447
\textbf{lemma} ``$\lbrakk i \le j;\> n \le (m{\Colon}\mathit{int})\rbrakk \,\Longrightarrow\, i * n + j * m \le i * m + j * n$'' \\
blanchet@33191
   448
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   449
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   450
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   451
\hbox{}\qquad\qquad $i = 0$ \\
blanchet@33191
   452
\hbox{}\qquad\qquad $j = 1$ \\
blanchet@33191
   453
\hbox{}\qquad\qquad $m = 1$ \\
blanchet@33191
   454
\hbox{}\qquad\qquad $n = 0$
blanchet@33191
   455
\postw
blanchet@33191
   456
blanchet@34124
   457
Internally, Nitpick uses either a unary or a binary representation of numbers.
blanchet@34124
   458
The unary representation is more efficient but only suitable for numbers very
blanchet@34124
   459
close to zero. By default, Nitpick attempts to choose the more appropriate
blanchet@34124
   460
encoding by inspecting the formula at hand. This behavior can be overridden by
blanchet@34124
   461
passing either \textit{unary\_ints} or \textit{binary\_ints} as option. For
blanchet@34124
   462
binary notation, the number of bits to use can be specified using
blanchet@34124
   463
the \textit{bits} option. For example:
blanchet@34124
   464
blanchet@34124
   465
\prew
blanchet@34124
   466
\textbf{nitpick} [\textit{binary\_ints}, \textit{bits}${} = 16$]
blanchet@34124
   467
\postw
blanchet@34124
   468
blanchet@33191
   469
With infinite types, we don't always have the luxury of a genuine counterexample
blanchet@33191
   470
and must often content ourselves with a potential one. The tedious task of
blanchet@33191
   471
finding out whether the potential counterexample is in fact genuine can be
blanchet@34124
   472
outsourced to \textit{auto} by passing \textit{check\_potential}. For example:
blanchet@33191
   473
blanchet@33191
   474
\prew
blanchet@33191
   475
\textbf{lemma} ``$\forall n.\; \textit{Suc}~n \mathbin{\not=} n \,\Longrightarrow\, P$'' \\
blanchet@34124
   476
\textbf{nitpick} [\textit{card~nat}~= 100, \textit{check\_potential}] \\[2\smallskipamount]
blanchet@33191
   477
\slshape Nitpick found a potential counterexample: \\[2\smallskipamount]
blanchet@33191
   478
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   479
\hbox{}\qquad\qquad $P = \textit{False}$ \\[2\smallskipamount]
blanchet@33191
   480
Confirmation by ``\textit{auto}'': The above counterexample is genuine.
blanchet@33191
   481
\postw
blanchet@33191
   482
blanchet@33191
   483
You might wonder why the counterexample is first reported as potential. The root
blanchet@33191
   484
of the problem is that the bound variable in $\forall n.\; \textit{Suc}~n
blanchet@33191
   485
\mathbin{\not=} n$ ranges over an infinite type. If Nitpick finds an $n$ such
blanchet@33191
   486
that $\textit{Suc}~n \mathbin{=} n$, it evaluates the assumption to
blanchet@33191
   487
\textit{False}; but otherwise, it does not know anything about values of $n \ge
blanchet@33191
   488
\textit{card~nat}$ and must therefore evaluate the assumption to $\unk$, not
blanchet@33191
   489
\textit{True}. Since the assumption can never be satisfied, the putative lemma
blanchet@33191
   490
can never be falsified.
blanchet@33191
   491
blanchet@33191
   492
Incidentally, if you distrust the so-called genuine counterexamples, you can
blanchet@33191
   493
enable \textit{check\_\allowbreak genuine} to verify them as well. However, be
blanchet@34124
   494
aware that \textit{auto} will usually fail to prove that the counterexample is
blanchet@33191
   495
genuine or spurious.
blanchet@33191
   496
blanchet@33191
   497
Some conjectures involving elementary number theory make Nitpick look like a
blanchet@33191
   498
giant with feet of clay:
blanchet@33191
   499
blanchet@33191
   500
\prew
blanchet@33191
   501
\textbf{lemma} ``$P~\textit{Suc}$'' \\
blanchet@33191
   502
\textbf{nitpick} [\textit{card} = 1--6] \\[2\smallskipamount]
blanchet@33191
   503
\slshape
blanchet@33191
   504
Nitpick found no counterexample.
blanchet@33191
   505
\postw
blanchet@33191
   506
blanchet@34124
   507
On any finite set $N$, \textit{Suc} is a partial function; for example, if $N =
blanchet@34124
   508
\{0, 1, \ldots, k\}$, then \textit{Suc} is $\{0 \mapsto 1,\, 1 \mapsto 2,\,
blanchet@34124
   509
\ldots,\, k \mapsto \unk\}$, which evaluates to $\unk$ when passed as
blanchet@34124
   510
argument to $P$. As a result, $P~\textit{Suc}$ is always $\unk$. The next
blanchet@34124
   511
example is similar:
blanchet@33191
   512
blanchet@33191
   513
\prew
blanchet@33191
   514
\textbf{lemma} ``$P~(\textit{op}~{+}\Colon
blanchet@33191
   515
\textit{nat}\mathbin{\Rightarrow}\textit{nat}\mathbin{\Rightarrow}\textit{nat})$'' \\
blanchet@33191
   516
\textbf{nitpick} [\textit{card nat} = 1] \\[2\smallskipamount]
blanchet@33191
   517
{\slshape Nitpick found a counterexample:} \\[2\smallskipamount]
blanchet@33191
   518
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   519
\hbox{}\qquad\qquad $P = \{\}$ \\[2\smallskipamount]
blanchet@33191
   520
\textbf{nitpick} [\textit{card nat} = 2] \\[2\smallskipamount]
blanchet@33191
   521
{\slshape Nitpick found no counterexample.}
blanchet@33191
   522
\postw
blanchet@33191
   523
blanchet@33191
   524
The problem here is that \textit{op}~+ is total when \textit{nat} is taken to be
blanchet@33191
   525
$\{0\}$ but becomes partial as soon as we add $1$, because $1 + 1 \notin \{0,
blanchet@33191
   526
1\}$.
blanchet@33191
   527
blanchet@33191
   528
Because numbers are infinite and are approximated using a three-valued logic,
blanchet@33191
   529
there is usually no need to systematically enumerate domain sizes. If Nitpick
blanchet@33191
   530
cannot find a genuine counterexample for \textit{card~nat}~= $k$, it is very
blanchet@33191
   531
unlikely that one could be found for smaller domains. (The $P~(\textit{op}~{+})$
blanchet@33191
   532
example above is an exception to this principle.) Nitpick nonetheless enumerates
blanchet@33191
   533
all cardinalities from 1 to 8 for \textit{nat}, mainly because smaller
blanchet@33191
   534
cardinalities are fast to handle and give rise to simpler counterexamples. This
blanchet@33191
   535
is explained in more detail in \S\ref{scope-monotonicity}.
blanchet@33191
   536
blanchet@33191
   537
\subsection{Inductive Datatypes}
blanchet@33191
   538
\label{inductive-datatypes}
blanchet@33191
   539
blanchet@33191
   540
Like natural numbers and integers, inductive datatypes with recursive
blanchet@33191
   541
constructors admit no finite models and must be approximated by a subterm-closed
blanchet@33191
   542
subset. For example, using a cardinality of 10 for ${'}a~\textit{list}$,
blanchet@33191
   543
Nitpick looks for all counterexamples that can be built using at most 10
blanchet@33191
   544
different lists.
blanchet@33191
   545
blanchet@33191
   546
Let's see with an example involving \textit{hd} (which returns the first element
blanchet@33191
   547
of a list) and $@$ (which concatenates two lists):
blanchet@33191
   548
blanchet@33191
   549
\prew
blanchet@33191
   550
\textbf{lemma} ``$\textit{hd}~(\textit{xs} \mathbin{@} [y, y]) = \textit{hd}~\textit{xs}$'' \\
blanchet@33191
   551
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   552
\slshape Nitpick found a counterexample for \textit{card} $'a$~= 3: \\[2\smallskipamount]
blanchet@33191
   553
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   554
\hbox{}\qquad\qquad $\textit{xs} = []$ \\
blanchet@33191
   555
\hbox{}\qquad\qquad $\textit{y} = a_3$
blanchet@33191
   556
\postw
blanchet@33191
   557
blanchet@33191
   558
To see why the counterexample is genuine, we enable \textit{show\_consts}
blanchet@33191
   559
and \textit{show\_\allowbreak datatypes}:
blanchet@33191
   560
blanchet@33191
   561
\prew
blanchet@33191
   562
{\slshape Datatype:} \\
blanchet@33191
   563
\hbox{}\qquad $'a$~\textit{list}~= $\{[],\, [a_3, a_3],\, [a_3],\, \unr\}$ \\
blanchet@33191
   564
{\slshape Constants:} \\
blanchet@33191
   565
\hbox{}\qquad $\lambda x_1.\; x_1 \mathbin{@} [y, y] = \undef([] := [a_3, a_3],\> [a_3, a_3] := \unk,\> [a_3] := \unk)$ \\
blanchet@33191
   566
\hbox{}\qquad $\textit{hd} = \undef([] := a_2,\> [a_3, a_3] := a_3,\> [a_3] := a_3)$
blanchet@33191
   567
\postw
blanchet@33191
   568
blanchet@33191
   569
Since $\mathit{hd}~[]$ is undefined in the logic, it may be given any value,
blanchet@33191
   570
including $a_2$.
blanchet@33191
   571
blanchet@33191
   572
The second constant, $\lambda x_1.\; x_1 \mathbin{@} [y, y]$, is simply the
blanchet@33191
   573
append operator whose second argument is fixed to be $[y, y]$. Appending $[a_3,
blanchet@33191
   574
a_3]$ to $[a_3]$ would normally give $[a_3, a_3, a_3]$, but this value is not
blanchet@33191
   575
representable in the subset of $'a$~\textit{list} considered by Nitpick, which
blanchet@33191
   576
is shown under the ``Datatype'' heading; hence the result is $\unk$. Similarly,
blanchet@33191
   577
appending $[a_3, a_3]$ to itself gives $\unk$.
blanchet@33191
   578
blanchet@33191
   579
Given \textit{card}~$'a = 3$ and \textit{card}~$'a~\textit{list} = 3$, Nitpick
blanchet@33191
   580
considers the following subsets:
blanchet@33191
   581
blanchet@33191
   582
\kern-.5\smallskipamount %% TYPESETTING
blanchet@33191
   583
blanchet@33191
   584
\prew
blanchet@33191
   585
\begin{multicols}{3}
blanchet@33191
   586
$\{[],\, [a_1],\, [a_2]\}$; \\
blanchet@33191
   587
$\{[],\, [a_1],\, [a_3]\}$; \\
blanchet@33191
   588
$\{[],\, [a_2],\, [a_3]\}$; \\
blanchet@33191
   589
$\{[],\, [a_1],\, [a_1, a_1]\}$; \\
blanchet@33191
   590
$\{[],\, [a_1],\, [a_2, a_1]\}$; \\
blanchet@33191
   591
$\{[],\, [a_1],\, [a_3, a_1]\}$; \\
blanchet@33191
   592
$\{[],\, [a_2],\, [a_1, a_2]\}$; \\
blanchet@33191
   593
$\{[],\, [a_2],\, [a_2, a_2]\}$; \\
blanchet@33191
   594
$\{[],\, [a_2],\, [a_3, a_2]\}$; \\
blanchet@33191
   595
$\{[],\, [a_3],\, [a_1, a_3]\}$; \\
blanchet@33191
   596
$\{[],\, [a_3],\, [a_2, a_3]\}$; \\
blanchet@33191
   597
$\{[],\, [a_3],\, [a_3, a_3]\}$.
blanchet@33191
   598
\end{multicols}
blanchet@33191
   599
\postw
blanchet@33191
   600
blanchet@33191
   601
\kern-2\smallskipamount %% TYPESETTING
blanchet@33191
   602
blanchet@33191
   603
All subterm-closed subsets of $'a~\textit{list}$ consisting of three values
blanchet@33191
   604
are listed and only those. As an example of a non-subterm-closed subset,
blanchet@33191
   605
consider $\mathcal{S} = \{[],\, [a_1],\,\allowbreak [a_1, a_3]\}$, and observe
blanchet@33191
   606
that $[a_1, a_3]$ (i.e., $a_1 \mathbin{\#} [a_3]$) has $[a_3] \notin
blanchet@33191
   607
\mathcal{S}$ as a subterm.
blanchet@33191
   608
blanchet@33191
   609
Here's another m\"ochtegern-lemma that Nitpick can refute without a blink:
blanchet@33191
   610
blanchet@33191
   611
\prew
blanchet@33191
   612
\textbf{lemma} ``$\lbrakk \textit{length}~\textit{xs} = 1;\> \textit{length}~\textit{ys} = 1
blanchet@33191
   613
\rbrakk \,\Longrightarrow\, \textit{xs} = \textit{ys}$''
blanchet@33191
   614
\\
blanchet@33191
   615
\textbf{nitpick} [\textit{show\_datatypes}] \\[2\smallskipamount]
blanchet@33191
   616
\slshape Nitpick found a counterexample for \textit{card} $'a$~= 3: \\[2\smallskipamount]
blanchet@33191
   617
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   618
\hbox{}\qquad\qquad $\textit{xs} = [a_2]$ \\
blanchet@33191
   619
\hbox{}\qquad\qquad $\textit{ys} = [a_3]$ \\
blanchet@33191
   620
\hbox{}\qquad Datatypes: \\
blanchet@33191
   621
\hbox{}\qquad\qquad $\textit{nat} = \{0,\, 1,\, 2,\, \unr\}$ \\
blanchet@33191
   622
\hbox{}\qquad\qquad $'a$~\textit{list} = $\{[],\, [a_3],\, [a_2],\, \unr\}$
blanchet@33191
   623
\postw
blanchet@33191
   624
blanchet@33191
   625
Because datatypes are approximated using a three-valued logic, there is usually
blanchet@33191
   626
no need to systematically enumerate cardinalities: If Nitpick cannot find a
blanchet@33191
   627
genuine counterexample for \textit{card}~$'a~\textit{list}$~= 10, it is very
blanchet@33191
   628
unlikely that one could be found for smaller cardinalities.
blanchet@33191
   629
blanchet@33191
   630
\subsection{Typedefs, Records, Rationals, and Reals}
blanchet@33191
   631
\label{typedefs-records-rationals-and-reals}
blanchet@33191
   632
blanchet@33191
   633
Nitpick generally treats types declared using \textbf{typedef} as datatypes
blanchet@33191
   634
whose single constructor is the corresponding \textit{Abs\_\kern.1ex} function.
blanchet@33191
   635
For example:
blanchet@33191
   636
blanchet@33191
   637
\prew
blanchet@33191
   638
\textbf{typedef}~\textit{three} = ``$\{0\Colon\textit{nat},\, 1,\, 2\}$'' \\
blanchet@33191
   639
\textbf{by}~\textit{blast} \\[2\smallskipamount]
blanchet@33191
   640
\textbf{definition}~$A \mathbin{\Colon} \textit{three}$ \textbf{where} ``\kern-.1em$A \,\equiv\, \textit{Abs\_\allowbreak three}~0$'' \\
blanchet@33191
   641
\textbf{definition}~$B \mathbin{\Colon} \textit{three}$ \textbf{where} ``$B \,\equiv\, \textit{Abs\_three}~1$'' \\
blanchet@33191
   642
\textbf{definition}~$C \mathbin{\Colon} \textit{three}$ \textbf{where} ``$C \,\equiv\, \textit{Abs\_three}~2$'' \\[2\smallskipamount]
blanchet@33191
   643
\textbf{lemma} ``$\lbrakk P~A;\> P~B\rbrakk \,\Longrightarrow\, P~x$'' \\
blanchet@33191
   644
\textbf{nitpick} [\textit{show\_datatypes}] \\[2\smallskipamount]
blanchet@33191
   645
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   646
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   647
\hbox{}\qquad\qquad $P = \{\Abs{1},\, \Abs{0}\}$ \\
blanchet@33191
   648
\hbox{}\qquad\qquad $x = \Abs{2}$ \\
blanchet@33191
   649
\hbox{}\qquad Datatypes: \\
blanchet@33191
   650
\hbox{}\qquad\qquad $\textit{nat} = \{0,\, 1,\, 2,\, \unr\}$ \\
blanchet@33191
   651
\hbox{}\qquad\qquad $\textit{three} = \{\Abs{2},\, \Abs{1},\, \Abs{0},\, \unr\}$
blanchet@33191
   652
\postw
blanchet@33191
   653
blanchet@33191
   654
%% MARK
blanchet@33191
   655
In the output above, $\Abs{n}$ abbreviates $\textit{Abs\_three}~n$.
blanchet@33191
   656
blanchet@33191
   657
%% MARK
blanchet@33191
   658
Records, which are implemented as \textbf{typedef}s behind the scenes, are
blanchet@33191
   659
handled in much the same way:
blanchet@33191
   660
blanchet@33191
   661
\prew
blanchet@33191
   662
\textbf{record} \textit{point} = \\
blanchet@33191
   663
\hbox{}\quad $\textit{Xcoord} \mathbin{\Colon} \textit{int}$ \\
blanchet@33191
   664
\hbox{}\quad $\textit{Ycoord} \mathbin{\Colon} \textit{int}$ \\[2\smallskipamount]
blanchet@33191
   665
\textbf{lemma} ``$\textit{Xcoord}~(p\Colon\textit{point}) = \textit{Xcoord}~(q\Colon\textit{point})$'' \\
blanchet@33191
   666
\textbf{nitpick} [\textit{show\_datatypes}] \\[2\smallskipamount]
blanchet@33191
   667
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   668
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   669
\hbox{}\qquad\qquad $p = \lparr\textit{Xcoord} = 0,\> \textit{Ycoord} = 0\rparr$ \\
blanchet@33191
   670
\hbox{}\qquad\qquad $q = \lparr\textit{Xcoord} = 1,\> \textit{Ycoord} = 1\rparr$ \\
blanchet@33191
   671
\hbox{}\qquad Datatypes: \\
blanchet@33191
   672
\hbox{}\qquad\qquad $\textit{int} = \{0,\, 1,\, \unr\}$ \\
blanchet@33191
   673
\hbox{}\qquad\qquad $\textit{point} = \{\lparr\textit{Xcoord} = 1,\>
blanchet@33191
   674
\textit{Ycoord} = 1\rparr,\> \lparr\textit{Xcoord} = 0,\> \textit{Ycoord} = 0\rparr,\, \unr\}$\kern-1pt %% QUIET
blanchet@33191
   675
\postw
blanchet@33191
   676
blanchet@33191
   677
Finally, Nitpick provides rudimentary support for rationals and reals using a
blanchet@33191
   678
similar approach:
blanchet@33191
   679
blanchet@33191
   680
\prew
blanchet@33191
   681
\textbf{lemma} ``$4 * x + 3 * (y\Colon\textit{real}) \not= 1/2$'' \\
blanchet@33191
   682
\textbf{nitpick} [\textit{show\_datatypes}] \\[2\smallskipamount]
blanchet@33191
   683
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   684
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   685
\hbox{}\qquad\qquad $x = 1/2$ \\
blanchet@33191
   686
\hbox{}\qquad\qquad $y = -1/2$ \\
blanchet@33191
   687
\hbox{}\qquad Datatypes: \\
blanchet@33191
   688
\hbox{}\qquad\qquad $\textit{nat} = \{0,\, 1,\, 2,\, 3,\, 4,\, 5,\, 6,\, 7,\, \unr\}$ \\
blanchet@33191
   689
\hbox{}\qquad\qquad $\textit{int} = \{0,\, 1,\, 2,\, 3,\, 4,\, -3,\, -2,\, -1,\, \unr\}$ \\
blanchet@33191
   690
\hbox{}\qquad\qquad $\textit{real} = \{1,\, 0,\, 4,\, -3/2,\, 3,\, 2,\, 1/2,\, -1/2,\, \unr\}$
blanchet@33191
   691
\postw
blanchet@33191
   692
blanchet@33191
   693
\subsection{Inductive and Coinductive Predicates}
blanchet@33191
   694
\label{inductive-and-coinductive-predicates}
blanchet@33191
   695
blanchet@33191
   696
Inductively defined predicates (and sets) are particularly problematic for
blanchet@33191
   697
counterexample generators. They can make Quickcheck~\cite{berghofer-nipkow-2004}
blanchet@33191
   698
loop forever and Refute~\cite{weber-2008} run out of resources. The crux of
blanchet@33191
   699
the problem is that they are defined using a least fixed point construction.
blanchet@33191
   700
blanchet@33191
   701
Nitpick's philosophy is that not all inductive predicates are equal. Consider
blanchet@33191
   702
the \textit{even} predicate below:
blanchet@33191
   703
blanchet@33191
   704
\prew
blanchet@33191
   705
\textbf{inductive}~\textit{even}~\textbf{where} \\
blanchet@33191
   706
``\textit{even}~0'' $\,\mid$ \\
blanchet@33191
   707
``\textit{even}~$n\,\Longrightarrow\, \textit{even}~(\textit{Suc}~(\textit{Suc}~n))$''
blanchet@33191
   708
\postw
blanchet@33191
   709
blanchet@33191
   710
This predicate enjoys the desirable property of being well-founded, which means
blanchet@33191
   711
that the introduction rules don't give rise to infinite chains of the form
blanchet@33191
   712
blanchet@33191
   713
\prew
blanchet@33191
   714
$\cdots\,\Longrightarrow\, \textit{even}~k''
blanchet@33191
   715
       \,\Longrightarrow\, \textit{even}~k'
blanchet@33191
   716
       \,\Longrightarrow\, \textit{even}~k.$
blanchet@33191
   717
\postw
blanchet@33191
   718
blanchet@33191
   719
For \textit{even}, this is obvious: Any chain ending at $k$ will be of length
blanchet@33191
   720
$k/2 + 1$:
blanchet@33191
   721
blanchet@33191
   722
\prew
blanchet@33191
   723
$\textit{even}~0\,\Longrightarrow\, \textit{even}~2\,\Longrightarrow\, \cdots
blanchet@33191
   724
       \,\Longrightarrow\, \textit{even}~(k - 2)
blanchet@33191
   725
       \,\Longrightarrow\, \textit{even}~k.$
blanchet@33191
   726
\postw
blanchet@33191
   727
blanchet@33191
   728
Wellfoundedness is desirable because it enables Nitpick to use a very efficient
blanchet@33191
   729
fixed point computation.%
blanchet@33191
   730
\footnote{If an inductive predicate is
blanchet@33191
   731
well-founded, then it has exactly one fixed point, which is simultaneously the
blanchet@33191
   732
least and the greatest fixed point. In these circumstances, the computation of
blanchet@33191
   733
the least fixed point amounts to the computation of an arbitrary fixed point,
blanchet@33191
   734
which can be performed using a straightforward recursive equation.}
blanchet@33191
   735
Moreover, Nitpick can prove wellfoundedness of most well-founded predicates,
blanchet@33191
   736
just as Isabelle's \textbf{function} package usually discharges termination
blanchet@33191
   737
proof obligations automatically.
blanchet@33191
   738
blanchet@33191
   739
Let's try an example:
blanchet@33191
   740
blanchet@33191
   741
\prew
blanchet@33191
   742
\textbf{lemma} ``$\exists n.\; \textit{even}~n \mathrel{\land} \textit{even}~(\textit{Suc}~n)$'' \\
blanchet@33191
   743
\textbf{nitpick}~[\textit{card nat}~= 100,\, \textit{verbose}] \\[2\smallskipamount]
blanchet@33191
   744
\slshape The inductive predicate ``\textit{even}'' was proved well-founded.
blanchet@33191
   745
Nitpick can compute it efficiently. \\[2\smallskipamount]
blanchet@33191
   746
Trying 1 scope: \\
blanchet@33191
   747
\hbox{}\qquad \textit{card nat}~= 100. \\[2\smallskipamount]
blanchet@33191
   748
Nitpick found a potential counterexample for \textit{card nat}~= 100: \\[2\smallskipamount]
blanchet@33191
   749
\hbox{}\qquad Empty assignment \\[2\smallskipamount]
blanchet@33191
   750
Nitpick could not find a better counterexample. \\[2\smallskipamount]
blanchet@33191
   751
Total time: 2274 ms.
blanchet@33191
   752
\postw
blanchet@33191
   753
blanchet@33191
   754
No genuine counterexample is possible because Nitpick cannot rule out the
blanchet@33191
   755
existence of a natural number $n \ge 100$ such that both $\textit{even}~n$ and
blanchet@33191
   756
$\textit{even}~(\textit{Suc}~n)$ are true. To help Nitpick, we can bound the
blanchet@33191
   757
existential quantifier:
blanchet@33191
   758
blanchet@33191
   759
\prew
blanchet@33191
   760
\textbf{lemma} ``$\exists n \mathbin{\le} 99.\; \textit{even}~n \mathrel{\land} \textit{even}~(\textit{Suc}~n)$'' \\
blanchet@33191
   761
\textbf{nitpick}~[\textit{card nat}~= 100] \\[2\smallskipamount]
blanchet@33191
   762
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   763
\hbox{}\qquad Empty assignment
blanchet@33191
   764
\postw
blanchet@33191
   765
blanchet@33191
   766
So far we were blessed by the wellfoundedness of \textit{even}. What happens if
blanchet@33191
   767
we use the following definition instead?
blanchet@33191
   768
blanchet@33191
   769
\prew
blanchet@33191
   770
\textbf{inductive} $\textit{even}'$ \textbf{where} \\
blanchet@33191
   771
``$\textit{even}'~(0{\Colon}\textit{nat})$'' $\,\mid$ \\
blanchet@33191
   772
``$\textit{even}'~2$'' $\,\mid$ \\
blanchet@33191
   773
``$\lbrakk\textit{even}'~m;\> \textit{even}'~n\rbrakk \,\Longrightarrow\, \textit{even}'~(m + n)$''
blanchet@33191
   774
\postw
blanchet@33191
   775
blanchet@33191
   776
This definition is not well-founded: From $\textit{even}'~0$ and
blanchet@33191
   777
$\textit{even}'~0$, we can derive that $\textit{even}'~0$. Nonetheless, the
blanchet@33191
   778
predicates $\textit{even}$ and $\textit{even}'$ are equivalent.
blanchet@33191
   779
blanchet@33191
   780
Let's check a property involving $\textit{even}'$. To make up for the
blanchet@33191
   781
foreseeable computational hurdles entailed by non-wellfoundedness, we decrease
blanchet@33191
   782
\textit{nat}'s cardinality to a mere 10:
blanchet@33191
   783
blanchet@33191
   784
\prew
blanchet@33191
   785
\textbf{lemma}~``$\exists n \in \{0, 2, 4, 6, 8\}.\;
blanchet@33191
   786
\lnot\;\textit{even}'~n$'' \\
blanchet@33191
   787
\textbf{nitpick}~[\textit{card nat}~= 10,\, \textit{verbose},\, \textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   788
\slshape
blanchet@33191
   789
The inductive predicate ``$\textit{even}'\!$'' could not be proved well-founded.
blanchet@33191
   790
Nitpick might need to unroll it. \\[2\smallskipamount]
blanchet@33191
   791
Trying 6 scopes: \\
blanchet@33191
   792
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 0; \\
blanchet@33191
   793
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 1; \\
blanchet@33191
   794
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 2; \\
blanchet@33191
   795
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 4; \\
blanchet@33191
   796
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 8; \\
blanchet@33191
   797
\hbox{}\qquad \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 9. \\[2\smallskipamount]
blanchet@33191
   798
Nitpick found a counterexample for \textit{card nat}~= 10 and \textit{iter} $\textit{even}'$~= 2: \\[2\smallskipamount]
blanchet@33191
   799
\hbox{}\qquad Constant: \nopagebreak \\
blanchet@33191
   800
\hbox{}\qquad\qquad $\lambda i.\; \textit{even}'$ = $\undef(\!\begin{aligned}[t]
blanchet@33191
   801
& 2 := \{0, 2, 4, 6, 8, 1^\Q, 3^\Q, 5^\Q, 7^\Q, 9^\Q\}, \\[-2pt]
blanchet@33191
   802
& 1 := \{0, 2, 4, 1^\Q, 3^\Q, 5^\Q, 6^\Q, 7^\Q, 8^\Q, 9^\Q\}, \\[-2pt]
blanchet@33191
   803
& 0 := \{0, 2, 1^\Q, 3^\Q, 4^\Q, 5^\Q, 6^\Q, 7^\Q, 8^\Q, 9^\Q\})\end{aligned}$ \\[2\smallskipamount]
blanchet@33191
   804
Total time: 1140 ms.
blanchet@33191
   805
\postw
blanchet@33191
   806
blanchet@33191
   807
Nitpick's output is very instructive. First, it tells us that the predicate is
blanchet@33191
   808
unrolled, meaning that it is computed iteratively from the empty set. Then it
blanchet@33191
   809
lists six scopes specifying different bounds on the numbers of iterations:\ 0,
blanchet@33191
   810
1, 2, 4, 8, and~9.
blanchet@33191
   811
blanchet@33191
   812
The output also shows how each iteration contributes to $\textit{even}'$. The
blanchet@33191
   813
notation $\lambda i.\; \textit{even}'$ indicates that the value of the
blanchet@33191
   814
predicate depends on an iteration counter. Iteration 0 provides the basis
blanchet@33191
   815
elements, $0$ and $2$. Iteration 1 contributes $4$ ($= 2 + 2$). Iteration 2
blanchet@33191
   816
throws $6$ ($= 2 + 4 = 4 + 2$) and $8$ ($= 4 + 4$) into the mix. Further
blanchet@33191
   817
iterations would not contribute any new elements.
blanchet@33191
   818
blanchet@33191
   819
Some values are marked with superscripted question
blanchet@33191
   820
marks~(`\lower.2ex\hbox{$^\Q$}'). These are the elements for which the
blanchet@33191
   821
predicate evaluates to $\unk$. Thus, $\textit{even}'$ evaluates to either
blanchet@33191
   822
\textit{True} or $\unk$, never \textit{False}.
blanchet@33191
   823
blanchet@33191
   824
When unrolling a predicate, Nitpick tries 0, 1, 2, 4, 8, 12, 16, and 24
blanchet@33191
   825
iterations. However, these numbers are bounded by the cardinality of the
blanchet@33191
   826
predicate's domain. With \textit{card~nat}~= 10, no more than 9 iterations are
blanchet@33191
   827
ever needed to compute the value of a \textit{nat} predicate. You can specify
blanchet@33191
   828
the number of iterations using the \textit{iter} option, as explained in
blanchet@33191
   829
\S\ref{scope-of-search}.
blanchet@33191
   830
blanchet@33191
   831
In the next formula, $\textit{even}'$ occurs both positively and negatively:
blanchet@33191
   832
blanchet@33191
   833
\prew
blanchet@33191
   834
\textbf{lemma} ``$\textit{even}'~(n - 2) \,\Longrightarrow\, \textit{even}'~n$'' \\
blanchet@34124
   835
\textbf{nitpick} [\textit{card nat} = 10, \textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   836
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
   837
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   838
\hbox{}\qquad\qquad $n = 1$ \\
blanchet@33191
   839
\hbox{}\qquad Constants: \nopagebreak \\
blanchet@33191
   840
\hbox{}\qquad\qquad $\lambda i.\; \textit{even}'$ = $\undef(\!\begin{aligned}[t]
blanchet@33191
   841
& 0 := \{0, 2, 1^\Q, 3^\Q, 4^\Q, 5^\Q, 6^\Q, 7^\Q, 8^\Q, 9^\Q\})\end{aligned}$  \\
blanchet@33191
   842
\hbox{}\qquad\qquad $\textit{even}' \subseteq \{0, 2, 4, 6, 8, \unr\}$
blanchet@33191
   843
\postw
blanchet@33191
   844
blanchet@33191
   845
Notice the special constraint $\textit{even}' \subseteq \{0,\, 2,\, 4,\, 6,\,
blanchet@33191
   846
8,\, \unr\}$ in the output, whose right-hand side represents an arbitrary
blanchet@33191
   847
fixed point (not necessarily the least one). It is used to falsify
blanchet@33191
   848
$\textit{even}'~n$. In contrast, the unrolled predicate is used to satisfy
blanchet@33191
   849
$\textit{even}'~(n - 2)$.
blanchet@33191
   850
blanchet@33191
   851
Coinductive predicates are handled dually. For example:
blanchet@33191
   852
blanchet@33191
   853
\prew
blanchet@33191
   854
\textbf{coinductive} \textit{nats} \textbf{where} \\
blanchet@33191
   855
``$\textit{nats}~(x\Colon\textit{nat}) \,\Longrightarrow\, \textit{nats}~x$'' \\[2\smallskipamount]
blanchet@33191
   856
\textbf{lemma} ``$\textit{nats} = \{0, 1, 2, 3, 4\}$'' \\
blanchet@33191
   857
\textbf{nitpick}~[\textit{card nat} = 10,\, \textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   858
\slshape Nitpick found a counterexample:
blanchet@33191
   859
\\[2\smallskipamount]
blanchet@33191
   860
\hbox{}\qquad Constants: \nopagebreak \\
blanchet@33191
   861
\hbox{}\qquad\qquad $\lambda i.\; \textit{nats} = \undef(0 := \{\!\begin{aligned}[t]
blanchet@33191
   862
& 0^\Q, 1^\Q, 2^\Q, 3^\Q, 4^\Q, 5^\Q, 6^\Q, 7^\Q, 8^\Q, 9^\Q, \\[-2pt]
blanchet@33191
   863
& \unr\})\end{aligned}$ \\
blanchet@33191
   864
\hbox{}\qquad\qquad $nats \supseteq \{9, 5^\Q, 6^\Q, 7^\Q, 8^\Q, \unr\}$
blanchet@33191
   865
\postw
blanchet@33191
   866
blanchet@33191
   867
As a special case, Nitpick uses Kodkod's transitive closure operator to encode
blanchet@33191
   868
negative occurrences of non-well-founded ``linear inductive predicates,'' i.e.,
blanchet@33191
   869
inductive predicates for which each the predicate occurs in at most one
blanchet@33191
   870
assumption of each introduction rule. For example:
blanchet@33191
   871
blanchet@33191
   872
\prew
blanchet@33191
   873
\textbf{inductive} \textit{odd} \textbf{where} \\
blanchet@33191
   874
``$\textit{odd}~1$'' $\,\mid$ \\
blanchet@33191
   875
``$\lbrakk \textit{odd}~m;\>\, \textit{even}~n\rbrakk \,\Longrightarrow\, \textit{odd}~(m + n)$'' \\[2\smallskipamount]
blanchet@33191
   876
\textbf{lemma}~``$\textit{odd}~n \,\Longrightarrow\, \textit{odd}~(n - 2)$'' \\
blanchet@33191
   877
\textbf{nitpick}~[\textit{card nat} = 10,\, \textit{show\_consts}] \\[2\smallskipamount]
blanchet@33191
   878
\slshape Nitpick found a counterexample:
blanchet@33191
   879
\\[2\smallskipamount]
blanchet@33191
   880
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
   881
\hbox{}\qquad\qquad $n = 1$ \\
blanchet@33191
   882
\hbox{}\qquad Constants: \nopagebreak \\
blanchet@33191
   883
\hbox{}\qquad\qquad $\textit{even} = \{0, 2, 4, 6, 8, \unr\}$ \\
blanchet@33191
   884
\hbox{}\qquad\qquad $\textit{odd}_{\textsl{base}} = \{1, \unr\}$ \\
blanchet@33191
   885
\hbox{}\qquad\qquad $\textit{odd}_{\textsl{step}} = \!
blanchet@33191
   886
\!\begin{aligned}[t]
blanchet@33191
   887
  & \{(0, 0), (0, 2), (0, 4), (0, 6), (0, 8), (1, 1), (1, 3), (1, 5), \\[-2pt]
blanchet@33191
   888
  & \phantom{\{} (1, 7), (1, 9), (2, 2), (2, 4), (2, 6), (2, 8), (3, 3),
blanchet@33191
   889
       (3, 5), \\[-2pt]
blanchet@33191
   890
  & \phantom{\{} (3, 7), (3, 9), (4, 4), (4, 6), (4, 8), (5, 5), (5, 7), (5, 9), \\[-2pt]
blanchet@33191
   891
  & \phantom{\{} (6, 6), (6, 8), (7, 7), (7, 9), (8, 8), (9, 9), \unr\}\end{aligned}$ \\
blanchet@33191
   892
\hbox{}\qquad\qquad $\textit{odd} \subseteq \{1, 3, 5, 7, 9, 8^\Q, \unr\}$
blanchet@33191
   893
\postw
blanchet@33191
   894
blanchet@33191
   895
\noindent
blanchet@33191
   896
In the output, $\textit{odd}_{\textrm{base}}$ represents the base elements and
blanchet@33191
   897
$\textit{odd}_{\textrm{step}}$ is a transition relation that computes new
blanchet@33191
   898
elements from known ones. The set $\textit{odd}$ consists of all the values
blanchet@33191
   899
reachable through the reflexive transitive closure of
blanchet@33191
   900
$\textit{odd}_{\textrm{step}}$ starting with any element from
blanchet@33191
   901
$\textit{odd}_{\textrm{base}}$, namely 1, 3, 5, 7, and 9. Using Kodkod's
blanchet@33191
   902
transitive closure to encode linear predicates is normally either more thorough
blanchet@33191
   903
or more efficient than unrolling (depending on the value of \textit{iter}), but
blanchet@33191
   904
for those cases where it isn't you can disable it by passing the
blanchet@33191
   905
\textit{dont\_star\_linear\_preds} option.
blanchet@33191
   906
blanchet@33191
   907
\subsection{Coinductive Datatypes}
blanchet@33191
   908
\label{coinductive-datatypes}
blanchet@33191
   909
blanchet@33191
   910
While Isabelle regrettably lacks a high-level mechanism for defining coinductive
blanchet@33191
   911
datatypes, the \textit{Coinductive\_List} theory provides a coinductive ``lazy
blanchet@33191
   912
list'' datatype, $'a~\textit{llist}$, defined the hard way. Nitpick supports
blanchet@33191
   913
these lazy lists seamlessly and provides a hook, described in
blanchet@33191
   914
\S\ref{registration-of-coinductive-datatypes}, to register custom coinductive
blanchet@33191
   915
datatypes.
blanchet@33191
   916
blanchet@33191
   917
(Co)intuitively, a coinductive datatype is similar to an inductive datatype but
blanchet@33191
   918
allows infinite objects. Thus, the infinite lists $\textit{ps}$ $=$ $[a, a, a,
blanchet@33191
   919
\ldots]$, $\textit{qs}$ $=$ $[a, b, a, b, \ldots]$, and $\textit{rs}$ $=$ $[0,
blanchet@33191
   920
1, 2, 3, \ldots]$ can be defined as lazy lists using the
blanchet@33191
   921
$\textit{LNil}\mathbin{\Colon}{'}a~\textit{llist}$ and
blanchet@33191
   922
$\textit{LCons}\mathbin{\Colon}{'}a \mathbin{\Rightarrow} {'}a~\textit{llist}
blanchet@33191
   923
\mathbin{\Rightarrow} {'}a~\textit{llist}$ constructors.
blanchet@33191
   924
blanchet@33191
   925
Although it is otherwise no friend of infinity, Nitpick can find counterexamples
blanchet@33191
   926
involving cyclic lists such as \textit{ps} and \textit{qs} above as well as
blanchet@33191
   927
finite lists:
blanchet@33191
   928
blanchet@33191
   929
\prew
blanchet@33191
   930
\textbf{lemma} ``$\textit{xs} \not= \textit{LCons}~a~\textit{xs}$'' \\
blanchet@33191
   931
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
   932
\slshape Nitpick found a counterexample for {\itshape card}~$'a$ = 1: \\[2\smallskipamount]
blanchet@33191
   933
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   934
\hbox{}\qquad\qquad $\textit{a} = a_1$ \\
blanchet@33191
   935
\hbox{}\qquad\qquad $\textit{xs} = \textsl{THE}~\omega.\; \omega = \textit{LCons}~a_1~\omega$
blanchet@33191
   936
\postw
blanchet@33191
   937
blanchet@33191
   938
The notation $\textrm{THE}~\omega.\; \omega = t(\omega)$ stands
blanchet@33191
   939
for the infinite term $t(t(t(\ldots)))$. Hence, \textit{xs} is simply the
blanchet@33191
   940
infinite list $[a_1, a_1, a_1, \ldots]$.
blanchet@33191
   941
blanchet@33191
   942
The next example is more interesting:
blanchet@33191
   943
blanchet@33191
   944
\prew
blanchet@33191
   945
\textbf{lemma}~``$\lbrakk\textit{xs} = \textit{LCons}~a~\textit{xs};\>\,
blanchet@33191
   946
\textit{ys} = \textit{iterates}~(\lambda b.\> a)~b\rbrakk \,\Longrightarrow\, \textit{xs} = \textit{ys}$'' \\
blanchet@33191
   947
\textbf{nitpick} [\textit{verbose}] \\[2\smallskipamount]
blanchet@33191
   948
\slshape The type ``\kern1pt$'a$'' passed the monotonicity test. Nitpick might be able to skip
blanchet@33191
   949
some scopes. \\[2\smallskipamount]
blanchet@33191
   950
Trying 8 scopes: \\
blanchet@33191
   951
\hbox{}\qquad \textit{card} $'a$~= 1, \textit{card} ``\kern1pt$'a~\textit{list}$''~= 1,
blanchet@33191
   952
and \textit{bisim\_depth}~= 0. \\
blanchet@33191
   953
\hbox{}\qquad $\qquad\vdots$ \\[.5\smallskipamount]
blanchet@33191
   954
\hbox{}\qquad \textit{card} $'a$~= 8, \textit{card} ``\kern1pt$'a~\textit{list}$''~= 8,
blanchet@33191
   955
and \textit{bisim\_depth}~= 7. \\[2\smallskipamount]
blanchet@33191
   956
Nitpick found a counterexample for {\itshape card}~$'a$ = 2,
blanchet@33191
   957
\textit{card}~``\kern1pt$'a~\textit{list}$''~= 2, and \textit{bisim\_\allowbreak
blanchet@33191
   958
depth}~= 1:
blanchet@33191
   959
\\[2\smallskipamount]
blanchet@33191
   960
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
   961
\hbox{}\qquad\qquad $\textit{a} = a_2$ \\
blanchet@33191
   962
\hbox{}\qquad\qquad $\textit{b} = a_1$ \\
blanchet@33191
   963
\hbox{}\qquad\qquad $\textit{xs} = \textsl{THE}~\omega.\; \omega = \textit{LCons}~a_2~\omega$ \\
blanchet@33191
   964
\hbox{}\qquad\qquad $\textit{ys} = \textit{LCons}~a_1~(\textsl{THE}~\omega.\; \omega = \textit{LCons}~a_2~\omega)$ \\[2\smallskipamount]
blanchet@33191
   965
Total time: 726 ms.
blanchet@33191
   966
\postw
blanchet@33191
   967
blanchet@33191
   968
The lazy list $\textit{xs}$ is simply $[a_2, a_2, a_2, \ldots]$, whereas
blanchet@33191
   969
$\textit{ys}$ is $[a_1, a_2, a_2, a_2, \ldots]$, i.e., a lasso-shaped list with
blanchet@33191
   970
$[a_1]$ as its stem and $[a_2]$ as its cycle. In general, the list segment
blanchet@33191
   971
within the scope of the {THE} binder corresponds to the lasso's cycle, whereas
blanchet@33191
   972
the segment leading to the binder is the stem.
blanchet@33191
   973
blanchet@33191
   974
A salient property of coinductive datatypes is that two objects are considered
blanchet@33191
   975
equal if and only if they lead to the same observations. For example, the lazy
blanchet@33191
   976
lists $\textrm{THE}~\omega.\; \omega =
blanchet@33191
   977
\textit{LCons}~a~(\textit{LCons}~b~\omega)$ and
blanchet@33191
   978
$\textit{LCons}~a~(\textrm{THE}~\omega.\; \omega =
blanchet@33191
   979
\textit{LCons}~b~(\textit{LCons}~a~\omega))$ are identical, because both lead
blanchet@33191
   980
to the sequence of observations $a$, $b$, $a$, $b$, \hbox{\ldots} (or,
blanchet@33191
   981
equivalently, both encode the infinite list $[a, b, a, b, \ldots]$). This
blanchet@33191
   982
concept of equality for coinductive datatypes is called bisimulation and is
blanchet@33191
   983
defined coinductively.
blanchet@33191
   984
blanchet@33191
   985
Internally, Nitpick encodes the coinductive bisimilarity predicate as part of
blanchet@33191
   986
the Kodkod problem to ensure that distinct objects lead to different
blanchet@33191
   987
observations. This precaution is somewhat expensive and often unnecessary, so it
blanchet@33191
   988
can be disabled by setting the \textit{bisim\_depth} option to $-1$. The
blanchet@33191
   989
bisimilarity check is then performed \textsl{after} the counterexample has been
blanchet@33191
   990
found to ensure correctness. If this after-the-fact check fails, the
blanchet@33191
   991
counterexample is tagged as ``likely genuine'' and Nitpick recommends to try
blanchet@33191
   992
again with \textit{bisim\_depth} set to a nonnegative integer. Disabling the
blanchet@33191
   993
check for the previous example saves approximately 150~milli\-seconds; the speed
blanchet@33191
   994
gains can be more significant for larger scopes.
blanchet@33191
   995
blanchet@33191
   996
The next formula illustrates the need for bisimilarity (either as a Kodkod
blanchet@33191
   997
predicate or as an after-the-fact check) to prevent spurious counterexamples:
blanchet@33191
   998
blanchet@33191
   999
\prew
blanchet@33191
  1000
\textbf{lemma} ``$\lbrakk xs = \textit{LCons}~a~\textit{xs};\>\, \textit{ys} = \textit{LCons}~a~\textit{ys}\rbrakk
blanchet@33191
  1001
\,\Longrightarrow\, \textit{xs} = \textit{ys}$'' \\
blanchet@34124
  1002
\textbf{nitpick} [\textit{bisim\_depth} = $-1$, \textit{show\_datatypes}] \\[2\smallskipamount]
blanchet@33191
  1003
\slshape Nitpick found a likely genuine counterexample for $\textit{card}~'a$ = 2: \\[2\smallskipamount]
blanchet@33191
  1004
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
  1005
\hbox{}\qquad\qquad $a = a_2$ \\
blanchet@33191
  1006
\hbox{}\qquad\qquad $\textit{xs} = \textsl{THE}~\omega.\; \omega =
blanchet@33191
  1007
\textit{LCons}~a_2~\omega$ \\
blanchet@33191
  1008
\hbox{}\qquad\qquad $\textit{ys} = \textsl{THE}~\omega.\; \omega = \textit{LCons}~a_2~\omega$ \\
blanchet@33191
  1009
\hbox{}\qquad Codatatype:\strut \nopagebreak \\
blanchet@33191
  1010
\hbox{}\qquad\qquad $'a~\textit{llist} =
blanchet@33191
  1011
\{\!\begin{aligned}[t]
blanchet@33191
  1012
  & \textsl{THE}~\omega.\; \omega = \textit{LCons}~a_2~\omega, \\[-2pt]
blanchet@33191
  1013
  & \textsl{THE}~\omega.\; \omega = \textit{LCons}~a_2~\omega,\> \unr\}\end{aligned}$
blanchet@33191
  1014
\\[2\smallskipamount]
blanchet@33191
  1015
Try again with ``\textit{bisim\_depth}'' set to a nonnegative value to confirm
blanchet@33191
  1016
that the counterexample is genuine. \\[2\smallskipamount]
blanchet@33191
  1017
{\upshape\textbf{nitpick}} \\[2\smallskipamount]
blanchet@33191
  1018
\slshape Nitpick found no counterexample.
blanchet@33191
  1019
\postw
blanchet@33191
  1020
blanchet@33191
  1021
In the first \textbf{nitpick} invocation, the after-the-fact check discovered 
blanchet@33191
  1022
that the two known elements of type $'a~\textit{llist}$ are bisimilar.
blanchet@33191
  1023
blanchet@33191
  1024
A compromise between leaving out the bisimilarity predicate from the Kodkod
blanchet@33191
  1025
problem and performing the after-the-fact check is to specify a lower
blanchet@33191
  1026
nonnegative \textit{bisim\_depth} value than the default one provided by
blanchet@33191
  1027
Nitpick. In general, a value of $K$ means that Nitpick will require all lists to
blanchet@33191
  1028
be distinguished from each other by their prefixes of length $K$. Be aware that
blanchet@33191
  1029
setting $K$ to a too low value can overconstrain Nitpick, preventing it from
blanchet@33191
  1030
finding any counterexamples.
blanchet@33191
  1031
blanchet@33191
  1032
\subsection{Boxing}
blanchet@33191
  1033
\label{boxing}
blanchet@33191
  1034
blanchet@33191
  1035
Nitpick normally maps function and product types directly to the corresponding
blanchet@33191
  1036
Kodkod concepts. As a consequence, if $'a$ has cardinality 3 and $'b$ has
blanchet@33191
  1037
cardinality 4, then $'a \times {'}b$ has cardinality 12 ($= 4 \times 3$) and $'a
blanchet@33191
  1038
\Rightarrow {'}b$ has cardinality 64 ($= 4^3$). In some circumstances, it pays
blanchet@33191
  1039
off to treat these types in the same way as plain datatypes, by approximating
blanchet@33191
  1040
them by a subset of a given cardinality. This technique is called ``boxing'' and
blanchet@33191
  1041
is particularly useful for functions passed as arguments to other functions, for
blanchet@33191
  1042
high-arity functions, and for large tuples. Under the hood, boxing involves
blanchet@33191
  1043
wrapping occurrences of the types $'a \times {'}b$ and $'a \Rightarrow {'}b$ in
blanchet@33191
  1044
isomorphic datatypes, as can be seen by enabling the \textit{debug} option.
blanchet@33191
  1045
blanchet@33191
  1046
To illustrate boxing, we consider a formalization of $\lambda$-terms represented
blanchet@33191
  1047
using de Bruijn's notation:
blanchet@33191
  1048
blanchet@33191
  1049
\prew
blanchet@33191
  1050
\textbf{datatype} \textit{tm} = \textit{Var}~\textit{nat}~$\mid$~\textit{Lam}~\textit{tm} $\mid$ \textit{App~tm~tm}
blanchet@33191
  1051
\postw
blanchet@33191
  1052
blanchet@33191
  1053
The $\textit{lift}~t~k$ function increments all variables with indices greater
blanchet@33191
  1054
than or equal to $k$ by one:
blanchet@33191
  1055
blanchet@33191
  1056
\prew
blanchet@33191
  1057
\textbf{primrec} \textit{lift} \textbf{where} \\
blanchet@33191
  1058
``$\textit{lift}~(\textit{Var}~j)~k = \textit{Var}~(\textrm{if}~j < k~\textrm{then}~j~\textrm{else}~j + 1)$'' $\mid$ \\
blanchet@33191
  1059
``$\textit{lift}~(\textit{Lam}~t)~k = \textit{Lam}~(\textit{lift}~t~(k + 1))$'' $\mid$ \\
blanchet@33191
  1060
``$\textit{lift}~(\textit{App}~t~u)~k = \textit{App}~(\textit{lift}~t~k)~(\textit{lift}~u~k)$''
blanchet@33191
  1061
\postw
blanchet@33191
  1062
blanchet@33191
  1063
The $\textit{loose}~t~k$ predicate returns \textit{True} if and only if
blanchet@33191
  1064
term $t$ has a loose variable with index $k$ or more:
blanchet@33191
  1065
blanchet@33191
  1066
\prew
blanchet@33191
  1067
\textbf{primrec}~\textit{loose} \textbf{where} \\
blanchet@33191
  1068
``$\textit{loose}~(\textit{Var}~j)~k = (j \ge k)$'' $\mid$ \\
blanchet@33191
  1069
``$\textit{loose}~(\textit{Lam}~t)~k = \textit{loose}~t~(\textit{Suc}~k)$'' $\mid$ \\
blanchet@33191
  1070
``$\textit{loose}~(\textit{App}~t~u)~k = (\textit{loose}~t~k \mathrel{\lor} \textit{loose}~u~k)$''
blanchet@33191
  1071
\postw
blanchet@33191
  1072
blanchet@33191
  1073
Next, the $\textit{subst}~\sigma~t$ function applies the substitution $\sigma$
blanchet@33191
  1074
on $t$:
blanchet@33191
  1075
blanchet@33191
  1076
\prew
blanchet@33191
  1077
\textbf{primrec}~\textit{subst} \textbf{where} \\
blanchet@33191
  1078
``$\textit{subst}~\sigma~(\textit{Var}~j) = \sigma~j$'' $\mid$ \\
blanchet@33191
  1079
``$\textit{subst}~\sigma~(\textit{Lam}~t) = {}$\phantom{''} \\
blanchet@33191
  1080
\phantom{``}$\textit{Lam}~(\textit{subst}~(\lambda n.\> \textrm{case}~n~\textrm{of}~0 \Rightarrow \textit{Var}~0 \mid \textit{Suc}~m \Rightarrow \textit{lift}~(\sigma~m)~1)~t)$'' $\mid$ \\
blanchet@33191
  1081
``$\textit{subst}~\sigma~(\textit{App}~t~u) = \textit{App}~(\textit{subst}~\sigma~t)~(\textit{subst}~\sigma~u)$''
blanchet@33191
  1082
\postw
blanchet@33191
  1083
blanchet@33191
  1084
A substitution is a function that maps variable indices to terms. Observe that
blanchet@33191
  1085
$\sigma$ is a function passed as argument and that Nitpick can't optimize it
blanchet@33191
  1086
away, because the recursive call for the \textit{Lam} case involves an altered
blanchet@33191
  1087
version. Also notice the \textit{lift} call, which increments the variable
blanchet@33191
  1088
indices when moving under a \textit{Lam}.
blanchet@33191
  1089
blanchet@33191
  1090
A reasonable property to expect of substitution is that it should leave closed
blanchet@33191
  1091
terms unchanged. Alas, even this simple property does not hold:
blanchet@33191
  1092
blanchet@33191
  1093
\pre
blanchet@33191
  1094
\textbf{lemma}~``$\lnot\,\textit{loose}~t~0 \,\Longrightarrow\, \textit{subst}~\sigma~t = t$'' \\
blanchet@33191
  1095
\textbf{nitpick} [\textit{verbose}] \\[2\smallskipamount]
blanchet@33191
  1096
\slshape
blanchet@33191
  1097
Trying 8 scopes: \nopagebreak \\
blanchet@33191
  1098
\hbox{}\qquad \textit{card~nat}~= 1, \textit{card tm}~= 1, and \textit{card} ``$\textit{nat} \Rightarrow \textit{tm}$'' = 1; \\
blanchet@33191
  1099
\hbox{}\qquad \textit{card~nat}~= 2, \textit{card tm}~= 2, and \textit{card} ``$\textit{nat} \Rightarrow \textit{tm}$'' = 2; \\
blanchet@33191
  1100
\hbox{}\qquad $\qquad\vdots$ \\[.5\smallskipamount]
blanchet@33191
  1101
\hbox{}\qquad \textit{card~nat}~= 8, \textit{card tm}~= 8, and \textit{card} ``$\textit{nat} \Rightarrow \textit{tm}$'' = 8. \\[2\smallskipamount]
blanchet@33191
  1102
Nitpick found a counterexample for \textit{card~nat}~= 6, \textit{card~tm}~= 6,
blanchet@33191
  1103
and \textit{card}~``$\textit{nat} \Rightarrow \textit{tm}$''~= 6: \\[2\smallskipamount]
blanchet@33191
  1104
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
  1105
\hbox{}\qquad\qquad $\sigma = \undef(\!\begin{aligned}[t]
blanchet@33191
  1106
& 0 := \textit{Var}~0,\>
blanchet@33191
  1107
  1 := \textit{Var}~0,\>
blanchet@33191
  1108
  2 := \textit{Var}~0, \\[-2pt]
blanchet@33191
  1109
& 3 := \textit{Var}~0,\>
blanchet@33191
  1110
  4 := \textit{Var}~0,\>
blanchet@33191
  1111
  5 := \textit{Var}~0)\end{aligned}$ \\
blanchet@33191
  1112
\hbox{}\qquad\qquad $t = \textit{Lam}~(\textit{Lam}~(\textit{Var}~1))$ \\[2\smallskipamount]
blanchet@33191
  1113
Total time: $4679$ ms.
blanchet@33191
  1114
\postw
blanchet@33191
  1115
blanchet@33191
  1116
Using \textit{eval}, we find out that $\textit{subst}~\sigma~t =
blanchet@33191
  1117
\textit{Lam}~(\textit{Lam}~(\textit{Var}~0))$. Using the traditional
blanchet@33191
  1118
$\lambda$-term notation, $t$~is
blanchet@33191
  1119
$\lambda x\, y.\> x$ whereas $\textit{subst}~\sigma~t$ is $\lambda x\, y.\> y$.
blanchet@33191
  1120
The bug is in \textit{subst}: The $\textit{lift}~(\sigma~m)~1$ call should be
blanchet@33191
  1121
replaced with $\textit{lift}~(\sigma~m)~0$.
blanchet@33191
  1122
blanchet@33191
  1123
An interesting aspect of Nitpick's verbose output is that it assigned inceasing
blanchet@33191
  1124
cardinalities from 1 to 8 to the type $\textit{nat} \Rightarrow \textit{tm}$.
blanchet@33191
  1125
For the formula of interest, knowing 6 values of that type was enough to find
blanchet@33191
  1126
the counterexample. Without boxing, $46\,656$ ($= 6^6$) values must be
blanchet@33191
  1127
considered, a hopeless undertaking:
blanchet@33191
  1128
blanchet@33191
  1129
\prew
blanchet@33191
  1130
\textbf{nitpick} [\textit{dont\_box}] \\[2\smallskipamount]
blanchet@33191
  1131
{\slshape Nitpick ran out of time after checking 4 of 8 scopes.}
blanchet@33191
  1132
\postw
blanchet@33191
  1133
blanchet@33191
  1134
{\looseness=-1
blanchet@33191
  1135
Boxing can be enabled or disabled globally or on a per-type basis using the
blanchet@33191
  1136
\textit{box} option. Moreover, setting the cardinality of a function or
blanchet@33191
  1137
product type implicitly enables boxing for that type. Nitpick usually performs
blanchet@33191
  1138
reasonable choices about which types should be boxed, but option tweaking
blanchet@33191
  1139
sometimes helps.
blanchet@33191
  1140
blanchet@33191
  1141
}
blanchet@33191
  1142
blanchet@33191
  1143
\subsection{Scope Monotonicity}
blanchet@33191
  1144
\label{scope-monotonicity}
blanchet@33191
  1145
blanchet@33191
  1146
The \textit{card} option (together with \textit{iter}, \textit{bisim\_depth},
blanchet@33191
  1147
and \textit{max}) controls which scopes are actually tested. In general, to
blanchet@33191
  1148
exhaust all models below a certain cardinality bound, the number of scopes that
blanchet@33191
  1149
Nitpick must consider increases exponentially with the number of type variables
blanchet@33191
  1150
(and \textbf{typedecl}'d types) occurring in the formula. Given the default
blanchet@33191
  1151
cardinality specification of 1--8, no fewer than $8^4 = 4096$ scopes must be
blanchet@33191
  1152
considered for a formula involving $'a$, $'b$, $'c$, and $'d$.
blanchet@33191
  1153
blanchet@33191
  1154
Fortunately, many formulas exhibit a property called \textsl{scope
blanchet@33191
  1155
monotonicity}, meaning that if the formula is falsifiable for a given scope,
blanchet@33191
  1156
it is also falsifiable for all larger scopes \cite[p.~165]{jackson-2006}.
blanchet@33191
  1157
blanchet@33191
  1158
Consider the formula
blanchet@33191
  1159
blanchet@33191
  1160
\prew
blanchet@33191
  1161
\textbf{lemma}~``$\textit{length~xs} = \textit{length~ys} \,\Longrightarrow\, \textit{rev}~(\textit{zip~xs~ys}) = \textit{zip~xs}~(\textit{rev~ys})$''
blanchet@33191
  1162
\postw
blanchet@33191
  1163
blanchet@33191
  1164
where \textit{xs} is of type $'a~\textit{list}$ and \textit{ys} is of type
blanchet@33191
  1165
$'b~\textit{list}$. A priori, Nitpick would need to consider 512 scopes to
blanchet@33191
  1166
exhaust the specification \textit{card}~= 1--8. However, our intuition tells us
blanchet@33191
  1167
that any counterexample found with a small scope would still be a counterexample
blanchet@33191
  1168
in a larger scope---by simply ignoring the fresh $'a$ and $'b$ values provided
blanchet@33191
  1169
by the larger scope. Nitpick comes to the same conclusion after a careful
blanchet@33191
  1170
inspection of the formula and the relevant definitions:
blanchet@33191
  1171
blanchet@33191
  1172
\prew
blanchet@33191
  1173
\textbf{nitpick}~[\textit{verbose}] \\[2\smallskipamount]
blanchet@33191
  1174
\slshape
blanchet@33191
  1175
The types ``\kern1pt$'a$'' and ``\kern1pt$'b$'' passed the monotonicity test.
blanchet@33191
  1176
Nitpick might be able to skip some scopes.
blanchet@33191
  1177
 \\[2\smallskipamount]
blanchet@33191
  1178
Trying 8 scopes: \\
blanchet@33191
  1179
\hbox{}\qquad \textit{card} $'a$~= 1, \textit{card} $'b$~= 1,
blanchet@33191
  1180
\textit{card} \textit{nat}~= 1, \textit{card} ``$('a \times {'}b)$
blanchet@33191
  1181
\textit{list}''~= 1, \\
blanchet@33191
  1182
\hbox{}\qquad\quad \textit{card} ``\kern1pt$'a$ \textit{list}''~= 1, and
blanchet@33191
  1183
\textit{card} ``\kern1pt$'b$ \textit{list}''~= 1. \\
blanchet@33191
  1184
\hbox{}\qquad \textit{card} $'a$~= 2, \textit{card} $'b$~= 2,
blanchet@33191
  1185
\textit{card} \textit{nat}~= 2, \textit{card} ``$('a \times {'}b)$
blanchet@33191
  1186
\textit{list}''~= 2, \\
blanchet@33191
  1187
\hbox{}\qquad\quad \textit{card} ``\kern1pt$'a$ \textit{list}''~= 2, and
blanchet@33191
  1188
\textit{card} ``\kern1pt$'b$ \textit{list}''~= 2. \\
blanchet@33191
  1189
\hbox{}\qquad $\qquad\vdots$ \\[.5\smallskipamount]
blanchet@33191
  1190
\hbox{}\qquad \textit{card} $'a$~= 8, \textit{card} $'b$~= 8,
blanchet@33191
  1191
\textit{card} \textit{nat}~= 8, \textit{card} ``$('a \times {'}b)$
blanchet@33191
  1192
\textit{list}''~= 8, \\
blanchet@33191
  1193
\hbox{}\qquad\quad \textit{card} ``\kern1pt$'a$ \textit{list}''~= 8, and
blanchet@33191
  1194
\textit{card} ``\kern1pt$'b$ \textit{list}''~= 8.
blanchet@33191
  1195
\\[2\smallskipamount]
blanchet@33191
  1196
Nitpick found a counterexample for
blanchet@33191
  1197
\textit{card} $'a$~= 5, \textit{card} $'b$~= 5,
blanchet@33191
  1198
\textit{card} \textit{nat}~= 5, \textit{card} ``$('a \times {'}b)$
blanchet@33191
  1199
\textit{list}''~= 5, \textit{card} ``\kern1pt$'a$ \textit{list}''~= 5, and
blanchet@33191
  1200
\textit{card} ``\kern1pt$'b$ \textit{list}''~= 5:
blanchet@33191
  1201
\\[2\smallskipamount]
blanchet@33191
  1202
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
  1203
\hbox{}\qquad\qquad $\textit{xs} = [a_4, a_5]$ \\
blanchet@33191
  1204
\hbox{}\qquad\qquad $\textit{ys} = [b_3, b_3]$ \\[2\smallskipamount]
blanchet@33191
  1205
Total time: 1636 ms.
blanchet@33191
  1206
\postw
blanchet@33191
  1207
blanchet@33191
  1208
In theory, it should be sufficient to test a single scope:
blanchet@33191
  1209
blanchet@33191
  1210
\prew
blanchet@33191
  1211
\textbf{nitpick}~[\textit{card}~= 8]
blanchet@33191
  1212
\postw
blanchet@33191
  1213
blanchet@33191
  1214
However, this is often less efficient in practice and may lead to overly complex
blanchet@33191
  1215
counterexamples.
blanchet@33191
  1216
blanchet@33191
  1217
If the monotonicity check fails but we believe that the formula is monotonic (or
blanchet@33191
  1218
we don't mind missing some counterexamples), we can pass the
blanchet@33191
  1219
\textit{mono} option. To convince yourself that this option is risky,
blanchet@33191
  1220
simply consider this example from \S\ref{skolemization}:
blanchet@33191
  1221
blanchet@33191
  1222
\prew
blanchet@33191
  1223
\textbf{lemma} ``$\exists g.\; \forall x\Colon 'b.~g~(f~x) = x
blanchet@33191
  1224
 \,\Longrightarrow\, \forall y\Colon {'}a.\; \exists x.~y = f~x$'' \\
blanchet@33191
  1225
\textbf{nitpick} [\textit{mono}] \\[2\smallskipamount]
blanchet@33191
  1226
{\slshape Nitpick found no counterexample.} \\[2\smallskipamount]
blanchet@33191
  1227
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1228
\slshape
blanchet@33191
  1229
Nitpick found a counterexample for \textit{card} $'a$~= 2 and \textit{card} $'b$~=~1: \\
blanchet@33191
  1230
\hbox{}\qquad $\vdots$
blanchet@33191
  1231
\postw
blanchet@33191
  1232
blanchet@33191
  1233
(It turns out the formula holds if and only if $\textit{card}~'a \le
blanchet@33191
  1234
\textit{card}~'b$.) Although this is rarely advisable, the automatic
blanchet@33191
  1235
monotonicity checks can be disabled by passing \textit{non\_mono}
blanchet@33191
  1236
(\S\ref{optimizations}).
blanchet@33191
  1237
blanchet@33191
  1238
As insinuated in \S\ref{natural-numbers-and-integers} and
blanchet@33191
  1239
\S\ref{inductive-datatypes}, \textit{nat}, \textit{int}, and inductive datatypes
blanchet@33191
  1240
are normally monotonic and treated as such. The same is true for record types,
blanchet@33191
  1241
\textit{rat}, \textit{real}, and some \textbf{typedef}'d types. Thus, given the
blanchet@33191
  1242
cardinality specification 1--8, a formula involving \textit{nat}, \textit{int},
blanchet@33191
  1243
\textit{int~list}, \textit{rat}, and \textit{rat~list} will lead Nitpick to
blanchet@33191
  1244
consider only 8~scopes instead of $32\,768$.
blanchet@33191
  1245
blanchet@33191
  1246
\section{Case Studies}
blanchet@33191
  1247
\label{case-studies}
blanchet@33191
  1248
blanchet@33191
  1249
As a didactic device, the previous section focused mostly on toy formulas whose
blanchet@33191
  1250
validity can easily be assessed just by looking at the formula. We will now
blanchet@33191
  1251
review two somewhat more realistic case studies that are within Nitpick's
blanchet@33191
  1252
reach:\ a context-free grammar modeled by mutually inductive sets and a
blanchet@33191
  1253
functional implementation of AA trees. The results presented in this
blanchet@33191
  1254
section were produced with the following settings:
blanchet@33191
  1255
blanchet@33191
  1256
\prew
blanchet@33191
  1257
\textbf{nitpick\_params} [\textit{max\_potential}~= 0,\, \textit{max\_threads} = 2]
blanchet@33191
  1258
\postw
blanchet@33191
  1259
blanchet@33191
  1260
\subsection{A Context-Free Grammar}
blanchet@33191
  1261
\label{a-context-free-grammar}
blanchet@33191
  1262
blanchet@33191
  1263
Our first case study is taken from section 7.4 in the Isabelle tutorial
blanchet@33191
  1264
\cite{isa-tutorial}. The following grammar, originally due to Hopcroft and
blanchet@33191
  1265
Ullman, produces all strings with an equal number of $a$'s and $b$'s:
blanchet@33191
  1266
blanchet@33191
  1267
\prew
blanchet@33191
  1268
\begin{tabular}{@{}r@{$\;\,$}c@{$\;\,$}l@{}}
blanchet@33191
  1269
$S$ & $::=$ & $\epsilon \mid bA \mid aB$ \\
blanchet@33191
  1270
$A$ & $::=$ & $aS \mid bAA$ \\
blanchet@33191
  1271
$B$ & $::=$ & $bS \mid aBB$
blanchet@33191
  1272
\end{tabular}
blanchet@33191
  1273
\postw
blanchet@33191
  1274
blanchet@33191
  1275
The intuition behind the grammar is that $A$ generates all string with one more
blanchet@33191
  1276
$a$ than $b$'s and $B$ generates all strings with one more $b$ than $a$'s.
blanchet@33191
  1277
blanchet@33191
  1278
The alphabet consists exclusively of $a$'s and $b$'s:
blanchet@33191
  1279
blanchet@33191
  1280
\prew
blanchet@33191
  1281
\textbf{datatype} \textit{alphabet}~= $a$ $\mid$ $b$
blanchet@33191
  1282
\postw
blanchet@33191
  1283
blanchet@33191
  1284
Strings over the alphabet are represented by \textit{alphabet list}s.
blanchet@33191
  1285
Nonterminals in the grammar become sets of strings. The production rules
blanchet@33191
  1286
presented above can be expressed as a mutually inductive definition:
blanchet@33191
  1287
blanchet@33191
  1288
\prew
blanchet@33191
  1289
\textbf{inductive\_set} $S$ \textbf{and} $A$ \textbf{and} $B$ \textbf{where} \\
blanchet@33191
  1290
\textit{R1}:\kern.4em ``$[] \in S$'' $\,\mid$ \\
blanchet@33191
  1291
\textit{R2}:\kern.4em ``$w \in A\,\Longrightarrow\, b \mathbin{\#} w \in S$'' $\,\mid$ \\
blanchet@33191
  1292
\textit{R3}:\kern.4em ``$w \in B\,\Longrightarrow\, a \mathbin{\#} w \in S$'' $\,\mid$ \\
blanchet@33191
  1293
\textit{R4}:\kern.4em ``$w \in S\,\Longrightarrow\, a \mathbin{\#} w \in A$'' $\,\mid$ \\
blanchet@33191
  1294
\textit{R5}:\kern.4em ``$w \in S\,\Longrightarrow\, b \mathbin{\#} w \in S$'' $\,\mid$ \\
blanchet@33191
  1295
\textit{R6}:\kern.4em ``$\lbrakk v \in B;\> v \in B\rbrakk \,\Longrightarrow\, a \mathbin{\#} v \mathbin{@} w \in B$''
blanchet@33191
  1296
\postw
blanchet@33191
  1297
blanchet@33191
  1298
The conversion of the grammar into the inductive definition was done manually by
blanchet@33191
  1299
Joe Blow, an underpaid undergraduate student. As a result, some errors might
blanchet@33191
  1300
have sneaked in.
blanchet@33191
  1301
blanchet@33191
  1302
Debugging faulty specifications is at the heart of Nitpick's \textsl{raison
blanchet@33191
  1303
d'\^etre}. A good approach is to state desirable properties of the specification
blanchet@33191
  1304
(here, that $S$ is exactly the set of strings over $\{a, b\}$ with as many $a$'s
blanchet@33191
  1305
as $b$'s) and check them with Nitpick. If the properties are correctly stated,
blanchet@33191
  1306
counterexamples will point to bugs in the specification. For our grammar
blanchet@33191
  1307
example, we will proceed in two steps, separating the soundness and the
blanchet@33191
  1308
completeness of the set $S$. First, soundness:
blanchet@33191
  1309
blanchet@33191
  1310
\prew
blanchet@33191
  1311
\textbf{theorem}~\textit{S\_sound}: \\
blanchet@33191
  1312
``$w \in S \longrightarrow \textit{length}~[x\mathbin{\leftarrow} w.\; x = a] =
blanchet@33191
  1313
  \textit{length}~[x\mathbin{\leftarrow} w.\; x = b]$'' \\
blanchet@33191
  1314
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1315
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
  1316
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
  1317
\hbox{}\qquad\qquad $w = [b]$
blanchet@33191
  1318
\postw
blanchet@33191
  1319
blanchet@33191
  1320
It would seem that $[b] \in S$. How could this be? An inspection of the
blanchet@33191
  1321
introduction rules reveals that the only rule with a right-hand side of the form
blanchet@33191
  1322
$b \mathbin{\#} {\ldots} \in S$ that could have introduced $[b]$ into $S$ is
blanchet@33191
  1323
\textit{R5}:
blanchet@33191
  1324
blanchet@33191
  1325
\prew
blanchet@33191
  1326
``$w \in S\,\Longrightarrow\, b \mathbin{\#} w \in S$''
blanchet@33191
  1327
\postw
blanchet@33191
  1328
blanchet@33191
  1329
On closer inspection, we can see that this rule is wrong. To match the
blanchet@33191
  1330
production $B ::= bS$, the second $S$ should be a $B$. We fix the typo and try
blanchet@33191
  1331
again:
blanchet@33191
  1332
blanchet@33191
  1333
\prew
blanchet@33191
  1334
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1335
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
  1336
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
  1337
\hbox{}\qquad\qquad $w = [a, a, b]$
blanchet@33191
  1338
\postw
blanchet@33191
  1339
blanchet@33191
  1340
Some detective work is necessary to find out what went wrong here. To get $[a,
blanchet@33191
  1341
a, b] \in S$, we need $[a, b] \in B$ by \textit{R3}, which in turn can only come
blanchet@33191
  1342
from \textit{R6}:
blanchet@33191
  1343
blanchet@33191
  1344
\prew
blanchet@33191
  1345
``$\lbrakk v \in B;\> v \in B\rbrakk \,\Longrightarrow\, a \mathbin{\#} v \mathbin{@} w \in B$''
blanchet@33191
  1346
\postw
blanchet@33191
  1347
blanchet@33191
  1348
Now, this formula must be wrong: The same assumption occurs twice, and the
blanchet@33191
  1349
variable $w$ is unconstrained. Clearly, one of the two occurrences of $v$ in
blanchet@33191
  1350
the assumptions should have been a $w$.
blanchet@33191
  1351
blanchet@33191
  1352
With the correction made, we don't get any counterexample from Nitpick. Let's
blanchet@33191
  1353
move on and check completeness:
blanchet@33191
  1354
blanchet@33191
  1355
\prew
blanchet@33191
  1356
\textbf{theorem}~\textit{S\_complete}: \\
blanchet@33191
  1357
``$\textit{length}~[x\mathbin{\leftarrow} w.\; x = a] =
blanchet@33191
  1358
   \textit{length}~[x\mathbin{\leftarrow} w.\; x = b]
blanchet@33191
  1359
  \longrightarrow w \in S$'' \\
blanchet@33191
  1360
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1361
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
  1362
\hbox{}\qquad Free variable: \nopagebreak \\
blanchet@33191
  1363
\hbox{}\qquad\qquad $w = [b, b, a, a]$
blanchet@33191
  1364
\postw
blanchet@33191
  1365
blanchet@33191
  1366
Apparently, $[b, b, a, a] \notin S$, even though it has the same numbers of
blanchet@33191
  1367
$a$'s and $b$'s. But since our inductive definition passed the soundness check,
blanchet@33191
  1368
the introduction rules we have are probably correct. Perhaps we simply lack an
blanchet@33191
  1369
introduction rule. Comparing the grammar with the inductive definition, our
blanchet@33191
  1370
suspicion is confirmed: Joe Blow simply forgot the production $A ::= bAA$,
blanchet@33191
  1371
without which the grammar cannot generate two or more $b$'s in a row. So we add
blanchet@33191
  1372
the rule
blanchet@33191
  1373
blanchet@33191
  1374
\prew
blanchet@33191
  1375
``$\lbrakk v \in A;\> w \in A\rbrakk \,\Longrightarrow\, b \mathbin{\#} v \mathbin{@} w \in A$''
blanchet@33191
  1376
\postw
blanchet@33191
  1377
blanchet@33191
  1378
With this last change, we don't get any counterexamples from Nitpick for either
blanchet@33191
  1379
soundness or completeness. We can even generalize our result to cover $A$ and
blanchet@33191
  1380
$B$ as well:
blanchet@33191
  1381
blanchet@33191
  1382
\prew
blanchet@33191
  1383
\textbf{theorem} \textit{S\_A\_B\_sound\_and\_complete}: \\
blanchet@33191
  1384
``$w \in S \longleftrightarrow \textit{length}~[x \mathbin{\leftarrow} w.\; x = a] = \textit{length}~[x \mathbin{\leftarrow} w.\; x = b]$'' \\
blanchet@33191
  1385
``$w \in A \longleftrightarrow \textit{length}~[x \mathbin{\leftarrow} w.\; x = a] = \textit{length}~[x \mathbin{\leftarrow} w.\; x = b] + 1$'' \\
blanchet@33191
  1386
``$w \in B \longleftrightarrow \textit{length}~[x \mathbin{\leftarrow} w.\; x = b] = \textit{length}~[x \mathbin{\leftarrow} w.\; x = a] + 1$'' \\
blanchet@33191
  1387
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1388
\slshape Nitpick found no counterexample.
blanchet@33191
  1389
\postw
blanchet@33191
  1390
blanchet@33191
  1391
\subsection{AA Trees}
blanchet@33191
  1392
\label{aa-trees}
blanchet@33191
  1393
blanchet@33191
  1394
AA trees are a kind of balanced trees discovered by Arne Andersson that provide
blanchet@33191
  1395
similar performance to red-black trees, but with a simpler implementation
blanchet@33191
  1396
\cite{andersson-1993}. They can be used to store sets of elements equipped with
blanchet@33191
  1397
a total order $<$. We start by defining the datatype and some basic extractor
blanchet@33191
  1398
functions:
blanchet@33191
  1399
blanchet@33191
  1400
\prew
blanchet@33191
  1401
\textbf{datatype} $'a$~\textit{tree} = $\Lambda$ $\mid$ $N$ ``\kern1pt$'a\Colon \textit{linorder}$'' \textit{nat} ``\kern1pt$'a$ \textit{tree}'' ``\kern1pt$'a$ \textit{tree}''  \\[2\smallskipamount]
blanchet@33191
  1402
\textbf{primrec} \textit{data} \textbf{where} \\
blanchet@33191
  1403
``$\textit{data}~\Lambda = \undef$'' $\,\mid$ \\
blanchet@33191
  1404
``$\textit{data}~(N~x~\_~\_~\_) = x$'' \\[2\smallskipamount]
blanchet@33191
  1405
\textbf{primrec} \textit{dataset} \textbf{where} \\
blanchet@33191
  1406
``$\textit{dataset}~\Lambda = \{\}$'' $\,\mid$ \\
blanchet@33191
  1407
``$\textit{dataset}~(N~x~\_~t~u) = \{x\} \cup \textit{dataset}~t \mathrel{\cup} \textit{dataset}~u$'' \\[2\smallskipamount]
blanchet@33191
  1408
\textbf{primrec} \textit{level} \textbf{where} \\
blanchet@33191
  1409
``$\textit{level}~\Lambda = 0$'' $\,\mid$ \\
blanchet@33191
  1410
``$\textit{level}~(N~\_~k~\_~\_) = k$'' \\[2\smallskipamount]
blanchet@33191
  1411
\textbf{primrec} \textit{left} \textbf{where} \\
blanchet@33191
  1412
``$\textit{left}~\Lambda = \Lambda$'' $\,\mid$ \\
blanchet@33191
  1413
``$\textit{left}~(N~\_~\_~t~\_) = t$'' \\[2\smallskipamount]
blanchet@33191
  1414
\textbf{primrec} \textit{right} \textbf{where} \\
blanchet@33191
  1415
``$\textit{right}~\Lambda = \Lambda$'' $\,\mid$ \\
blanchet@33191
  1416
``$\textit{right}~(N~\_~\_~\_~u) = u$''
blanchet@33191
  1417
\postw
blanchet@33191
  1418
blanchet@33191
  1419
The wellformedness criterion for AA trees is fairly complex. Wikipedia states it
blanchet@33191
  1420
as follows \cite{wikipedia-2009-aa-trees}:
blanchet@33191
  1421
blanchet@33191
  1422
\kern.2\parskip %% TYPESETTING
blanchet@33191
  1423
blanchet@33191
  1424
\pre
blanchet@33191
  1425
Each node has a level field, and the following invariants must remain true for
blanchet@33191
  1426
the tree to be valid:
blanchet@33191
  1427
blanchet@33191
  1428
\raggedright
blanchet@33191
  1429
blanchet@33191
  1430
\kern-.4\parskip %% TYPESETTING
blanchet@33191
  1431
blanchet@33191
  1432
\begin{enum}
blanchet@33191
  1433
\item[]
blanchet@33191
  1434
\begin{enum}
blanchet@33191
  1435
\item[1.] The level of a leaf node is one.
blanchet@33191
  1436
\item[2.] The level of a left child is strictly less than that of its parent.
blanchet@33191
  1437
\item[3.] The level of a right child is less than or equal to that of its parent.
blanchet@33191
  1438
\item[4.] The level of a right grandchild is strictly less than that of its grandparent.
blanchet@33191
  1439
\item[5.] Every node of level greater than one must have two children.
blanchet@33191
  1440
\end{enum}
blanchet@33191
  1441
\end{enum}
blanchet@33191
  1442
\post
blanchet@33191
  1443
blanchet@33191
  1444
\kern.4\parskip %% TYPESETTING
blanchet@33191
  1445
blanchet@33191
  1446
The \textit{wf} predicate formalizes this description:
blanchet@33191
  1447
blanchet@33191
  1448
\prew
blanchet@33191
  1449
\textbf{primrec} \textit{wf} \textbf{where} \\
blanchet@33191
  1450
``$\textit{wf}~\Lambda = \textit{True}$'' $\,\mid$ \\
blanchet@33191
  1451
``$\textit{wf}~(N~\_~k~t~u) =$ \\
blanchet@33191
  1452
\phantom{``}$(\textrm{if}~t = \Lambda~\textrm{then}$ \\
blanchet@33191
  1453
\phantom{``$(\quad$}$k = 1 \mathrel{\land} (u = \Lambda \mathrel{\lor} (\textit{level}~u = 1 \mathrel{\land} \textit{left}~u = \Lambda \mathrel{\land} \textit{right}~u = \Lambda))$ \\
blanchet@33191
  1454
\phantom{``$($}$\textrm{else}$ \\
blanchet@33193
  1455
\hbox{}\phantom{``$(\quad$}$\textit{wf}~t \mathrel{\land} \textit{wf}~u
blanchet@33191
  1456
\mathrel{\land} u \not= \Lambda \mathrel{\land} \textit{level}~t < k
blanchet@33193
  1457
\mathrel{\land} \textit{level}~u \le k$ \\
blanchet@33193
  1458
\hbox{}\phantom{``$(\quad$}${\land}\; \textit{level}~(\textit{right}~u) < k)$''
blanchet@33191
  1459
\postw
blanchet@33191
  1460
blanchet@33191
  1461
Rebalancing the tree upon insertion and removal of elements is performed by two
blanchet@33191
  1462
auxiliary functions called \textit{skew} and \textit{split}, defined below:
blanchet@33191
  1463
blanchet@33191
  1464
\prew
blanchet@33191
  1465
\textbf{primrec} \textit{skew} \textbf{where} \\
blanchet@33191
  1466
``$\textit{skew}~\Lambda = \Lambda$'' $\,\mid$ \\
blanchet@33191
  1467
``$\textit{skew}~(N~x~k~t~u) = {}$ \\
blanchet@33191
  1468
\phantom{``}$(\textrm{if}~t \not= \Lambda \mathrel{\land} k =
blanchet@33191
  1469
\textit{level}~t~\textrm{then}$ \\
blanchet@33191
  1470
\phantom{``(\quad}$N~(\textit{data}~t)~k~(\textit{left}~t)~(N~x~k~
blanchet@33191
  1471
(\textit{right}~t)~u)$ \\
blanchet@33191
  1472
\phantom{``(}$\textrm{else}$ \\
blanchet@33191
  1473
\phantom{``(\quad}$N~x~k~t~u)$''
blanchet@33191
  1474
\postw
blanchet@33191
  1475
blanchet@33191
  1476
\prew
blanchet@33191
  1477
\textbf{primrec} \textit{split} \textbf{where} \\
blanchet@33191
  1478
``$\textit{split}~\Lambda = \Lambda$'' $\,\mid$ \\
blanchet@33191
  1479
``$\textit{split}~(N~x~k~t~u) = {}$ \\
blanchet@33191
  1480
\phantom{``}$(\textrm{if}~u \not= \Lambda \mathrel{\land} k =
blanchet@33191
  1481
\textit{level}~(\textit{right}~u)~\textrm{then}$ \\
blanchet@33191
  1482
\phantom{``(\quad}$N~(\textit{data}~u)~(\textit{Suc}~k)~
blanchet@33191
  1483
(N~x~k~t~(\textit{left}~u))~(\textit{right}~u)$ \\
blanchet@33191
  1484
\phantom{``(}$\textrm{else}$ \\
blanchet@33191
  1485
\phantom{``(\quad}$N~x~k~t~u)$''
blanchet@33191
  1486
\postw
blanchet@33191
  1487
blanchet@33191
  1488
Performing a \textit{skew} or a \textit{split} should have no impact on the set
blanchet@33191
  1489
of elements stored in the tree:
blanchet@33191
  1490
blanchet@33191
  1491
\prew
blanchet@33191
  1492
\textbf{theorem}~\textit{dataset\_skew\_split}:\\
blanchet@33191
  1493
``$\textit{dataset}~(\textit{skew}~t) = \textit{dataset}~t$'' \\
blanchet@33191
  1494
``$\textit{dataset}~(\textit{split}~t) = \textit{dataset}~t$'' \\
blanchet@33191
  1495
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1496
{\slshape Nitpick ran out of time after checking 7 of 8 scopes.}
blanchet@33191
  1497
\postw
blanchet@33191
  1498
blanchet@33191
  1499
Furthermore, applying \textit{skew} or \textit{split} to a well-formed tree
blanchet@33191
  1500
should not alter the tree:
blanchet@33191
  1501
blanchet@33191
  1502
\prew
blanchet@33191
  1503
\textbf{theorem}~\textit{wf\_skew\_split}:\\
blanchet@33191
  1504
``$\textit{wf}~t\,\Longrightarrow\, \textit{skew}~t = t$'' \\
blanchet@33191
  1505
``$\textit{wf}~t\,\Longrightarrow\, \textit{split}~t = t$'' \\
blanchet@33191
  1506
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1507
{\slshape Nitpick found no counterexample.}
blanchet@33191
  1508
\postw
blanchet@33191
  1509
blanchet@33191
  1510
Insertion is implemented recursively. It preserves the sort order:
blanchet@33191
  1511
blanchet@33191
  1512
\prew
blanchet@33191
  1513
\textbf{primrec}~\textit{insort} \textbf{where} \\
blanchet@33191
  1514
``$\textit{insort}~\Lambda~x = N~x~1~\Lambda~\Lambda$'' $\,\mid$ \\
blanchet@33191
  1515
``$\textit{insort}~(N~y~k~t~u)~x =$ \\
blanchet@33191
  1516
\phantom{``}$({*}~(\textit{split} \circ \textit{skew})~{*})~(N~y~k~(\textrm{if}~x < y~\textrm{then}~\textit{insort}~t~x~\textrm{else}~t)$ \\
blanchet@33191
  1517
\phantom{``$({*}~(\textit{split} \circ \textit{skew})~{*})~(N~y~k~$}$(\textrm{if}~x > y~\textrm{then}~\textit{insort}~u~x~\textrm{else}~u))$''
blanchet@33191
  1518
\postw
blanchet@33191
  1519
blanchet@33191
  1520
Notice that we deliberately commented out the application of \textit{skew} and
blanchet@33191
  1521
\textit{split}. Let's see if this causes any problems:
blanchet@33191
  1522
blanchet@33191
  1523
\prew
blanchet@33191
  1524
\textbf{theorem}~\textit{wf\_insort}:\kern.4em ``$\textit{wf}~t\,\Longrightarrow\, \textit{wf}~(\textit{insort}~t~x)$'' \\
blanchet@33191
  1525
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1526
\slshape Nitpick found a counterexample for \textit{card} $'a$ = 4: \\[2\smallskipamount]
blanchet@33191
  1527
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
  1528
\hbox{}\qquad\qquad $t = N~a_3~1~\Lambda~\Lambda$ \\
blanchet@33191
  1529
\hbox{}\qquad\qquad $x = a_4$ \\[2\smallskipamount]
blanchet@33191
  1530
\postw
blanchet@33191
  1531
blanchet@34038
  1532
It's hard to see why this is a counterexample. To improve readability, we will
blanchet@34038
  1533
restrict the theorem to \textit{nat}, so that we don't need to look up the value
blanchet@34038
  1534
of the $\textit{op}~{<}$ constant to find out which element is smaller than the
blanchet@34038
  1535
other. In addition, we will tell Nitpick to display the value of
blanchet@34038
  1536
$\textit{insort}~t~x$ using the \textit{eval} option. This gives
blanchet@33191
  1537
blanchet@33191
  1538
\prew
blanchet@33191
  1539
\textbf{theorem} \textit{wf\_insort\_nat}:\kern.4em ``$\textit{wf}~t\,\Longrightarrow\, \textit{wf}~(\textit{insort}~t~(x\Colon\textit{nat}))$'' \\
blanchet@33191
  1540
\textbf{nitpick} [\textit{eval} = ``$\textit{insort}~t~x$''] \\[2\smallskipamount]
blanchet@33191
  1541
\slshape Nitpick found a counterexample: \\[2\smallskipamount]
blanchet@33191
  1542
\hbox{}\qquad Free variables: \nopagebreak \\
blanchet@33191
  1543
\hbox{}\qquad\qquad $t = N~1~1~\Lambda~\Lambda$ \\
blanchet@33191
  1544
\hbox{}\qquad\qquad $x = 0$ \\
blanchet@33191
  1545
\hbox{}\qquad Evaluated term: \\
blanchet@33191
  1546
\hbox{}\qquad\qquad $\textit{insort}~t~x = N~1~1~(N~0~1~\Lambda~\Lambda)~\Lambda$
blanchet@33191
  1547
\postw
blanchet@33191
  1548
blanchet@33191
  1549
Nitpick's output reveals that the element $0$ was added as a left child of $1$,
blanchet@33191
  1550
where both have a level of 1. This violates the second AA tree invariant, which
blanchet@33191
  1551
states that a left child's level must be less than its parent's. This shouldn't
blanchet@33191
  1552
come as a surprise, considering that we commented out the tree rebalancing code.
blanchet@33191
  1553
Reintroducing the code seems to solve the problem:
blanchet@33191
  1554
blanchet@33191
  1555
\prew
blanchet@33191
  1556
\textbf{theorem}~\textit{wf\_insort}:\kern.4em ``$\textit{wf}~t\,\Longrightarrow\, \textit{wf}~(\textit{insort}~t~x)$'' \\
blanchet@33191
  1557
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1558
{\slshape Nitpick ran out of time after checking 6 of 8 scopes.}
blanchet@33191
  1559
\postw
blanchet@33191
  1560
blanchet@33191
  1561
Insertion should transform the set of elements represented by the tree in the
blanchet@33191
  1562
obvious way:
blanchet@33191
  1563
blanchet@33191
  1564
\prew
blanchet@33191
  1565
\textbf{theorem} \textit{dataset\_insort}:\kern.4em
blanchet@33191
  1566
``$\textit{dataset}~(\textit{insort}~t~x) = \{x\} \cup \textit{dataset}~t$'' \\
blanchet@33191
  1567
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  1568
{\slshape Nitpick ran out of time after checking 5 of 8 scopes.}
blanchet@33191
  1569
\postw
blanchet@33191
  1570
blanchet@33191
  1571
We could continue like this and sketch a complete theory of AA trees without
blanchet@33191
  1572
performing a single proof. Once the definitions and main theorems are in place
blanchet@33191
  1573
and have been thoroughly tested using Nitpick, we could start working on the
blanchet@33191
  1574
proofs. Developing theories this way usually saves time, because faulty theorems
blanchet@33191
  1575
and definitions are discovered much earlier in the process.
blanchet@33191
  1576
blanchet@33191
  1577
\section{Option Reference}
blanchet@33191
  1578
\label{option-reference}
blanchet@33191
  1579
blanchet@33191
  1580
\def\flushitem#1{\item[]\noindent\kern-\leftmargin \textbf{#1}}
blanchet@33191
  1581
\def\qty#1{$\left<\textit{#1}\right>$}
blanchet@33191
  1582
\def\qtybf#1{$\mathbf{\left<\textbf{\textit{#1}}\right>}$}
blanchet@33191
  1583
\def\optrue#1#2{\flushitem{\textit{#1} $\bigl[$= \qtybf{bool}$\bigr]$\quad [\textit{true}]\hfill (neg.: \textit{#2})}\nopagebreak\\[\parskip]}
blanchet@33191
  1584
\def\opfalse#1#2{\flushitem{\textit{#1} $\bigl[$= \qtybf{bool}$\bigr]$\quad [\textit{false}]\hfill (neg.: \textit{#2})}\nopagebreak\\[\parskip]}
blanchet@33191
  1585
\def\opsmart#1#2{\flushitem{\textit{#1} $\bigl[$= \qtybf{bool\_or\_smart}$\bigr]$\quad [\textit{smart}]\hfill (neg.: \textit{#2})}\nopagebreak\\[\parskip]}
blanchet@33191
  1586
\def\ops#1#2{\flushitem{\textit{#1} = \qtybf{#2}} \nopagebreak\\[\parskip]}
blanchet@33191
  1587
\def\opt#1#2#3{\flushitem{\textit{#1} = \qtybf{#2}\quad [\textit{#3}]} \nopagebreak\\[\parskip]}
blanchet@33191
  1588
\def\opu#1#2#3{\flushitem{\textit{#1} \qtybf{#2} = \qtybf{#3}} \nopagebreak\\[\parskip]}
blanchet@33191
  1589
\def\opusmart#1#2#3{\flushitem{\textit{#1} \qtybf{#2} $\bigl[$= \qtybf{bool\_or\_smart}$\bigr]$\hfill (neg.: \textit{#3})}\nopagebreak\\[\parskip]}
blanchet@33191
  1590
blanchet@33191
  1591
Nitpick's behavior can be influenced by various options, which can be specified
blanchet@33191
  1592
in brackets after the \textbf{nitpick} command. Default values can be set
blanchet@33191
  1593
using \textbf{nitpick\_\allowbreak params}. For example:
blanchet@33191
  1594
blanchet@33191
  1595
\prew
blanchet@33191
  1596
\textbf{nitpick\_params} [\textit{verbose}, \,\textit{timeout} = 60$\,s$]
blanchet@33191
  1597
\postw
blanchet@33191
  1598
blanchet@33191
  1599
The options are categorized as follows:\ mode of operation
blanchet@33191
  1600
(\S\ref{mode-of-operation}), scope of search (\S\ref{scope-of-search}), output
blanchet@33191
  1601
format (\S\ref{output-format}), automatic counterexample checks
blanchet@33191
  1602
(\S\ref{authentication}), optimizations
blanchet@33191
  1603
(\S\ref{optimizations}), and timeouts (\S\ref{timeouts}).
blanchet@33191
  1604
blanchet@33561
  1605
You can instruct Nitpick to run automatically on newly entered theorems by
blanchet@33561
  1606
enabling the ``Auto Nitpick'' option from the ``Isabelle'' menu in Proof
blanchet@33561
  1607
General. For automatic runs, \textit{user\_axioms} (\S\ref{mode-of-operation})
blanchet@33561
  1608
and \textit{assms} (\S\ref{mode-of-operation}) are implicitly enabled,
blanchet@33561
  1609
\textit{blocking} (\S\ref{mode-of-operation}), \textit{verbose}
blanchet@33561
  1610
(\S\ref{output-format}), and \textit{debug} (\S\ref{output-format}) are
blanchet@33561
  1611
disabled, \textit{max\_potential} (\S\ref{output-format}) is taken to be 0, and
blanchet@33561
  1612
\textit{timeout} (\S\ref{timeouts}) is superseded by the ``Auto Counterexample
blanchet@33561
  1613
Time Limit'' in Proof General's ``Isabelle'' menu. Nitpick's output is also more
blanchet@33561
  1614
concise.
blanchet@33561
  1615
blanchet@33191
  1616
The number of options can be overwhelming at first glance. Do not let that worry
blanchet@33191
  1617
you: Nitpick's defaults have been chosen so that it almost always does the right
blanchet@33191
  1618
thing, and the most important options have been covered in context in
blanchet@33191
  1619
\S\ref{first-steps}.
blanchet@33191
  1620
blanchet@33191
  1621
The descriptions below refer to the following syntactic quantities:
blanchet@33191
  1622
blanchet@33191
  1623
\begin{enum}
blanchet@33191
  1624
\item[$\bullet$] \qtybf{string}: A string.
blanchet@33191
  1625
\item[$\bullet$] \qtybf{bool}: \textit{true} or \textit{false}.
blanchet@33191
  1626
\item[$\bullet$] \qtybf{bool\_or\_smart}: \textit{true}, \textit{false}, or \textit{smart}.
blanchet@33191
  1627
\item[$\bullet$] \qtybf{int}: An integer. Negative integers are prefixed with a hyphen.
blanchet@33191
  1628
\item[$\bullet$] \qtybf{int\_or\_smart}: An integer or \textit{smart}.
blanchet@33191
  1629
\item[$\bullet$] \qtybf{int\_range}: An integer (e.g., 3) or a range
blanchet@33191
  1630
of nonnegative integers (e.g., $1$--$4$). The range symbol `--' can be entered as \texttt{-} (hyphen) or \texttt{\char`\\\char`\<midarrow\char`\>}.
blanchet@33191
  1631
blanchet@33191
  1632
\item[$\bullet$] \qtybf{int\_seq}: A comma-separated sequence of ranges of integers (e.g.,~1{,}3{,}\allowbreak6--8).
blanchet@33191
  1633
\item[$\bullet$] \qtybf{time}: An integer followed by $\textit{min}$ (minutes), $s$ (seconds), or \textit{ms}
blanchet@33191
  1634
(milliseconds), or the keyword \textit{none} ($\infty$ years).
blanchet@33191
  1635
\item[$\bullet$] \qtybf{const}: The name of a HOL constant.
blanchet@33191
  1636
\item[$\bullet$] \qtybf{term}: A HOL term (e.g., ``$f~x$'').
blanchet@33191
  1637
\item[$\bullet$] \qtybf{term\_list}: A space-separated list of HOL terms (e.g.,
blanchet@33191
  1638
``$f~x$''~``$g~y$'').
blanchet@33191
  1639
\item[$\bullet$] \qtybf{type}: A HOL type.
blanchet@33191
  1640
\end{enum}
blanchet@33191
  1641
blanchet@33191
  1642
Default values are indicated in square brackets. Boolean options have a negated
blanchet@33561
  1643
counterpart (e.g., \textit{blocking} vs.\ \textit{no\_blocking}). When setting
blanchet@33561
  1644
Boolean options, ``= \textit{true}'' may be omitted.
blanchet@33191
  1645
blanchet@33191
  1646
\subsection{Mode of Operation}
blanchet@33191
  1647
\label{mode-of-operation}
blanchet@33191
  1648
blanchet@33191
  1649
\begin{enum}
blanchet@33191
  1650
\optrue{blocking}{non\_blocking}
blanchet@33191
  1651
Specifies whether the \textbf{nitpick} command should operate synchronously.
blanchet@33191
  1652
The asynchronous (non-blocking) mode lets the user start proving the putative
blanchet@33191
  1653
theorem while Nitpick looks for a counterexample, but it can also be more
blanchet@33191
  1654
confusing. For technical reasons, automatic runs currently always block.
blanchet@33191
  1655
blanchet@33191
  1656
\optrue{falsify}{satisfy}
blanchet@33191
  1657
Specifies whether Nitpick should look for falsifying examples (countermodels) or
blanchet@33191
  1658
satisfying examples (models). This manual assumes throughout that
blanchet@33191
  1659
\textit{falsify} is enabled.
blanchet@33191
  1660
blanchet@33191
  1661
\opsmart{user\_axioms}{no\_user\_axioms}
blanchet@33191
  1662
Specifies whether the user-defined axioms (specified using 
blanchet@33191
  1663
\textbf{axiomatization} and \textbf{axioms}) should be considered. If the option
blanchet@33191
  1664
is set to \textit{smart}, Nitpick performs an ad hoc axiom selection based on
blanchet@33191
  1665
the constants that occur in the formula to falsify. The option is implicitly set
blanchet@33191
  1666
to \textit{true} for automatic runs.
blanchet@33191
  1667
blanchet@33191
  1668
\textbf{Warning:} If the option is set to \textit{true}, Nitpick might
blanchet@33191
  1669
nonetheless ignore some polymorphic axioms. Counterexamples generated under
blanchet@33191
  1670
these conditions are tagged as ``likely genuine.'' The \textit{debug}
blanchet@33191
  1671
(\S\ref{output-format}) option can be used to find out which axioms were
blanchet@33191
  1672
considered.
blanchet@33191
  1673
blanchet@33191
  1674
\nopagebreak
blanchet@33561
  1675
{\small See also \textit{assms} (\S\ref{mode-of-operation}) and \textit{debug}
blanchet@33561
  1676
(\S\ref{output-format}).}
blanchet@33191
  1677
blanchet@33191
  1678
\optrue{assms}{no\_assms}
blanchet@33191
  1679
Specifies whether the relevant assumptions in structured proof should be
blanchet@33191
  1680
considered. The option is implicitly enabled for automatic runs.
blanchet@33191
  1681
blanchet@33191
  1682
\nopagebreak
blanchet@33561
  1683
{\small See also \textit{user\_axioms} (\S\ref{mode-of-operation}).}
blanchet@33191
  1684
blanchet@33191
  1685
\opfalse{overlord}{no\_overlord}
blanchet@33191
  1686
Specifies whether Nitpick should put its temporary files in
blanchet@33191
  1687
\texttt{\$ISABELLE\_\allowbreak HOME\_\allowbreak USER}, which is useful for
blanchet@33191
  1688
debugging Nitpick but also unsafe if several instances of the tool are run
blanchet@33196
  1689
simultaneously.
blanchet@33191
  1690
blanchet@33191
  1691
\nopagebreak
blanchet@33191
  1692
{\small See also \textit{debug} (\S\ref{output-format}).}
blanchet@33191
  1693
\end{enum}
blanchet@33191
  1694
blanchet@33191
  1695
\subsection{Scope of Search}
blanchet@33191
  1696
\label{scope-of-search}
blanchet@33191
  1697
blanchet@33191
  1698
\begin{enum}
blanchet@33191
  1699
\opu{card}{type}{int\_seq}
blanchet@34124
  1700
Specifies the sequence of cardinalities to use for a given type.
blanchet@33191
  1701
For free types, and often also for \textbf{typedecl}'d types, it usually makes
blanchet@33191
  1702
sense to specify cardinalities as a range of the form \textit{$1$--$n$}.
blanchet@33191
  1703
Although function and product types are normally mapped directly to the
blanchet@33191
  1704
corresponding Kodkod concepts, setting
blanchet@33191
  1705
the cardinality of such types is also allowed and implicitly enables ``boxing''
blanchet@33191
  1706
for them, as explained in the description of the \textit{box}~\qty{type}
blanchet@33191
  1707
and \textit{box} (\S\ref{scope-of-search}) options.
blanchet@33191
  1708
blanchet@33191
  1709
\nopagebreak
blanchet@33191
  1710
{\small See also \textit{mono} (\S\ref{scope-of-search}).}
blanchet@33191
  1711
blanchet@33191
  1712
\opt{card}{int\_seq}{$\mathbf{1}$--$\mathbf{8}$}
blanchet@33191
  1713
Specifies the default sequence of cardinalities to use. This can be overridden
blanchet@33191
  1714
on a per-type basis using the \textit{card}~\qty{type} option described above.
blanchet@33191
  1715
blanchet@33191
  1716
\opu{max}{const}{int\_seq}
blanchet@33191
  1717
Specifies the sequence of maximum multiplicities to use for a given
blanchet@33191
  1718
(co)in\-duc\-tive datatype constructor. A constructor's multiplicity is the
blanchet@33191
  1719
number of distinct values that it can construct. Nonsensical values (e.g.,
blanchet@33191
  1720
\textit{max}~[]~$=$~2) are silently repaired. This option is only available for
blanchet@33191
  1721
datatypes equipped with several constructors.
blanchet@33191
  1722
blanchet@33191
  1723
\ops{max}{int\_seq}
blanchet@33191
  1724
Specifies the default sequence of maximum multiplicities to use for
blanchet@33191
  1725
(co)in\-duc\-tive datatype constructors. This can be overridden on a per-constructor
blanchet@33191
  1726
basis using the \textit{max}~\qty{const} option described above.
blanchet@33191
  1727
blanchet@34124
  1728
\opsmart{binary\_ints}{unary\_ints}
blanchet@34124
  1729
Specifies whether natural numbers and integers should be encoded using a unary
blanchet@34124
  1730
or binary notation. In unary mode, the cardinality fully specifies the subset
blanchet@34124
  1731
used to approximate the type. For example:
blanchet@34124
  1732
%
blanchet@34124
  1733
$$\hbox{\begin{tabular}{@{}rll@{}}%
blanchet@34124
  1734
\textit{card nat} = 4 & induces & $\{0,\, 1,\, 2,\, 3\}$ \\
blanchet@34124
  1735
\textit{card int} = 4 & induces & $\{-1,\, 0,\, +1,\, +2\}$ \\
blanchet@34124
  1736
\textit{card int} = 5 & induces & $\{-2,\, -1,\, 0,\, +1,\, +2\}.$%
blanchet@34124
  1737
\end{tabular}}$$
blanchet@34124
  1738
%
blanchet@34124
  1739
In general:
blanchet@34124
  1740
%
blanchet@34124
  1741
$$\hbox{\begin{tabular}{@{}rll@{}}%
blanchet@34124
  1742
\textit{card nat} = $K$ & induces & $\{0,\, \ldots,\, K - 1\}$ \\
blanchet@34124
  1743
\textit{card int} = $K$ & induces & $\{-\lceil K/2 \rceil + 1,\, \ldots,\, +\lfloor K/2 \rfloor\}.$%
blanchet@34124
  1744
\end{tabular}}$$
blanchet@34124
  1745
%
blanchet@34124
  1746
In binary mode, the cardinality specifies the number of distinct values that can
blanchet@34124
  1747
be constructed. Each of these value is represented by a bit pattern whose length
blanchet@34124
  1748
is specified by the \textit{bits} (\S\ref{scope-of-search}) option. By default,
blanchet@34124
  1749
Nitpick attempts to choose the more appropriate encoding by inspecting the
blanchet@34124
  1750
formula at hand, preferring the binary notation for problems involving
blanchet@34124
  1751
multiplicative operators or large constants.
blanchet@34124
  1752
blanchet@34124
  1753
\textbf{Warning:} For technical reasons, Nitpick always reverts to unary for
blanchet@34124
  1754
problems that refer to the types \textit{rat} or \textit{real} or the constants
blanchet@34124
  1755
\textit{gcd} or \textit{lcm}.
blanchet@34124
  1756
blanchet@34124
  1757
{\small See also \textit{bits} (\S\ref{scope-of-search}) and
blanchet@34124
  1758
\textit{show\_datatypes} (\S\ref{output-format}).}
blanchet@34124
  1759
blanchet@34124
  1760
\opt{bits}{int\_seq}{$\mathbf{1},\mathbf{2},\mathbf{3},\mathbf{4},\mathbf{6},\mathbf{8},\mathbf{10},\mathbf{12}$}
blanchet@34124
  1761
Specifies the number of bits to use to represent natural numbers and integers in
blanchet@34124
  1762
binary, excluding the sign bit. The minimum is 1 and the maximum is 31.
blanchet@34124
  1763
blanchet@34124
  1764
{\small See also \textit{binary\_ints} (\S\ref{scope-of-search}).}
blanchet@34124
  1765
blanchet@33191
  1766
\opusmart{wf}{const}{non\_wf}
blanchet@33191
  1767
Specifies whether the specified (co)in\-duc\-tively defined predicate is
blanchet@33191
  1768
well-founded. The option can take the following values:
blanchet@33191
  1769
blanchet@33191
  1770
\begin{enum}
blanchet@33191
  1771
\item[$\bullet$] \textbf{\textit{true}}: Tentatively treat the (co)in\-duc\-tive
blanchet@33191
  1772
predicate as if it were well-founded. Since this is generally not sound when the
blanchet@33191
  1773
predicate is not well-founded, the counterexamples are tagged as ``likely
blanchet@33191
  1774
genuine.''
blanchet@33191
  1775
blanchet@33191
  1776
\item[$\bullet$] \textbf{\textit{false}}: Treat the (co)in\-duc\-tive predicate
blanchet@33191
  1777
as if it were not well-founded. The predicate is then unrolled as prescribed by
blanchet@33191
  1778
the \textit{star\_linear\_preds}, \textit{iter}~\qty{const}, and \textit{iter}
blanchet@33191
  1779
options.
blanchet@33191
  1780
blanchet@33191
  1781
\item[$\bullet$] \textbf{\textit{smart}}: Try to prove that the inductive
blanchet@33191
  1782
predicate is well-founded using Isabelle's \textit{lexicographic\_order} and
blanchet@33191
  1783
\textit{sizechange} tactics. If this succeeds (or the predicate occurs with an
blanchet@33191
  1784
appropriate polarity in the formula to falsify), use an efficient fixed point
blanchet@33191
  1785
equation as specification of the predicate; otherwise, unroll the predicates
blanchet@33191
  1786
according to the \textit{iter}~\qty{const} and \textit{iter} options.
blanchet@33191
  1787
\end{enum}
blanchet@33191
  1788
blanchet@33191
  1789
\nopagebreak
blanchet@33191
  1790
{\small See also \textit{iter} (\S\ref{scope-of-search}),
blanchet@33191
  1791
\textit{star\_linear\_preds} (\S\ref{optimizations}), and \textit{tac\_timeout}
blanchet@33191
  1792
(\S\ref{timeouts}).}
blanchet@33191
  1793
blanchet@33191
  1794
\opsmart{wf}{non\_wf}
blanchet@33191
  1795
Specifies the default wellfoundedness setting to use. This can be overridden on
blanchet@33191
  1796
a per-predicate basis using the \textit{wf}~\qty{const} option above.
blanchet@33191
  1797
blanchet@33191
  1798
\opu{iter}{const}{int\_seq}
blanchet@33191
  1799
Specifies the sequence of iteration counts to use when unrolling a given
blanchet@33191
  1800
(co)in\-duc\-tive predicate. By default, unrolling is applied for inductive
blanchet@33191
  1801
predicates that occur negatively and coinductive predicates that occur
blanchet@33191
  1802
positively in the formula to falsify and that cannot be proved to be
blanchet@33191
  1803
well-founded, but this behavior is influenced by the \textit{wf} option. The
blanchet@33191
  1804
iteration counts are automatically bounded by the cardinality of the predicate's
blanchet@33191
  1805
domain.
blanchet@33191
  1806
blanchet@33191
  1807
{\small See also \textit{wf} (\S\ref{scope-of-search}) and
blanchet@33191
  1808
\textit{star\_linear\_preds} (\S\ref{optimizations}).}
blanchet@33191
  1809
blanchet@33191
  1810
\opt{iter}{int\_seq}{$\mathbf{1{,}2{,}4{,}8{,}12{,}16{,}24{,}32}$}
blanchet@33191
  1811
Specifies the sequence of iteration counts to use when unrolling (co)in\-duc\-tive
blanchet@33191
  1812
predicates. This can be overridden on a per-predicate basis using the
blanchet@33191
  1813
\textit{iter} \qty{const} option above.
blanchet@33191
  1814
blanchet@33191
  1815
\opt{bisim\_depth}{int\_seq}{$\mathbf{7}$}
blanchet@33191
  1816
Specifies the sequence of iteration counts to use when unrolling the
blanchet@33191
  1817
bisimilarity predicate generated by Nitpick for coinductive datatypes. A value
blanchet@33191
  1818
of $-1$ means that no predicate is generated, in which case Nitpick performs an
blanchet@33191
  1819
after-the-fact check to see if the known coinductive datatype values are
blanchet@33191
  1820
bidissimilar. If two values are found to be bisimilar, the counterexample is
blanchet@33191
  1821
tagged as ``likely genuine.'' The iteration counts are automatically bounded by
blanchet@33191
  1822
the sum of the cardinalities of the coinductive datatypes occurring in the
blanchet@33191
  1823
formula to falsify.
blanchet@33191
  1824
blanchet@33191
  1825
\opusmart{box}{type}{dont\_box}
blanchet@33191
  1826
Specifies whether Nitpick should attempt to wrap (``box'') a given function or
blanchet@33191
  1827
product type in an isomorphic datatype internally. Boxing is an effective mean
blanchet@33191
  1828
to reduce the search space and speed up Nitpick, because the isomorphic datatype
blanchet@33191
  1829
is approximated by a subset of the possible function or pair values;
blanchet@33191
  1830
like other drastic optimizations, it can also prevent the discovery of
blanchet@33191
  1831
counterexamples. The option can take the following values:
blanchet@33191
  1832
blanchet@33191
  1833
\begin{enum}
blanchet@33191
  1834
\item[$\bullet$] \textbf{\textit{true}}: Box the specified type whenever
blanchet@33191
  1835
practicable.
blanchet@33191
  1836
\item[$\bullet$] \textbf{\textit{false}}: Never box the type.
blanchet@33191
  1837
\item[$\bullet$] \textbf{\textit{smart}}: Box the type only in contexts where it
blanchet@33191
  1838
is likely to help. For example, $n$-tuples where $n > 2$ and arguments to
blanchet@33191
  1839
higher-order functions are good candidates for boxing.
blanchet@33191
  1840
\end{enum}
blanchet@33191
  1841
blanchet@33191
  1842
Setting the \textit{card}~\qty{type} option for a function or product type
blanchet@33191
  1843
implicitly enables boxing for that type.
blanchet@33191
  1844
blanchet@33191
  1845
\nopagebreak
blanchet@33191
  1846
{\small See also \textit{verbose} (\S\ref{output-format})
blanchet@33191
  1847
and \textit{debug} (\S\ref{output-format}).}
blanchet@33191
  1848
blanchet@33191
  1849
\opsmart{box}{dont\_box}
blanchet@33191
  1850
Specifies the default boxing setting to use. This can be overridden on a
blanchet@33191
  1851
per-type basis using the \textit{box}~\qty{type} option described above.
blanchet@33191
  1852
blanchet@33191
  1853
\opusmart{mono}{type}{non\_mono}
blanchet@33191
  1854
Specifies whether the specified type should be considered monotonic when
blanchet@33191
  1855
enumerating scopes. If the option is set to \textit{smart}, Nitpick performs a
blanchet@33191
  1856
monotonicity check on the type. Setting this option to \textit{true} can reduce
blanchet@33191
  1857
the number of scopes tried, but it also diminishes the theoretical chance of
blanchet@33191
  1858
finding a counterexample, as demonstrated in \S\ref{scope-monotonicity}.
blanchet@33191
  1859
blanchet@33191
  1860
\nopagebreak
blanchet@33191
  1861
{\small See also \textit{card} (\S\ref{scope-of-search}),
blanchet@33556
  1862
\textit{merge\_type\_vars} (\S\ref{scope-of-search}), and \textit{verbose}
blanchet@33191
  1863
(\S\ref{output-format}).}
blanchet@33191
  1864
blanchet@33191
  1865
\opsmart{mono}{non\_box}
blanchet@33191
  1866
Specifies the default monotonicity setting to use. This can be overridden on a
blanchet@33191
  1867
per-type basis using the \textit{mono}~\qty{type} option described above.
blanchet@33191
  1868
blanchet@33556
  1869
\opfalse{merge\_type\_vars}{dont\_merge\_type\_vars}
blanchet@33191
  1870
Specifies whether type variables with the same sort constraints should be
blanchet@33191
  1871
merged. Setting this option to \textit{true} can reduce the number of scopes
blanchet@33191
  1872
tried and the size of the generated Kodkod formulas, but it also diminishes the
blanchet@33191
  1873
theoretical chance of finding a counterexample.
blanchet@33191
  1874
blanchet@33191
  1875
{\small See also \textit{mono} (\S\ref{scope-of-search}).}
blanchet@33191
  1876
\end{enum}
blanchet@33191
  1877
blanchet@33191
  1878
\subsection{Output Format}
blanchet@33191
  1879
\label{output-format}
blanchet@33191
  1880
blanchet@33191
  1881
\begin{enum}
blanchet@33191
  1882
\opfalse{verbose}{quiet}
blanchet@33191
  1883
Specifies whether the \textbf{nitpick} command should explain what it does. This
blanchet@33191
  1884
option is useful to determine which scopes are tried or which SAT solver is
blanchet@33191
  1885
used. This option is implicitly disabled for automatic runs.
blanchet@33191
  1886
blanchet@33191
  1887
\opfalse{debug}{no\_debug}
blanchet@33191
  1888
Specifies whether Nitpick should display additional debugging information beyond
blanchet@33191
  1889
what \textit{verbose} already displays. Enabling \textit{debug} also enables
blanchet@33191
  1890
\textit{verbose} and \textit{show\_all} behind the scenes. The \textit{debug}
blanchet@33191
  1891
option is implicitly disabled for automatic runs.
blanchet@33191
  1892
blanchet@33191
  1893
\nopagebreak
blanchet@33561
  1894
{\small See also \textit{overlord} (\S\ref{mode-of-operation}) and
blanchet@33561
  1895
\textit{batch\_size} (\S\ref{optimizations}).}
blanchet@33191
  1896
blanchet@33191
  1897
\optrue{show\_skolems}{hide\_skolem}
blanchet@33191
  1898
Specifies whether the values of Skolem constants should be displayed as part of
blanchet@33191
  1899
counterexamples. Skolem constants correspond to bound variables in the original
blanchet@33191
  1900
formula and usually help us to understand why the counterexample falsifies the
blanchet@33191
  1901
formula.
blanchet@33191
  1902
blanchet@33191
  1903
\nopagebreak
blanchet@33191
  1904
{\small See also \textit{skolemize} (\S\ref{optimizations}).}
blanchet@33191
  1905
blanchet@33191
  1906
\opfalse{show\_datatypes}{hide\_datatypes}
blanchet@33191
  1907
Specifies whether the subsets used to approximate (co)in\-duc\-tive datatypes should
blanchet@33191
  1908
be displayed as part of counterexamples. Such subsets are sometimes helpful when
blanchet@33191
  1909
investigating whether a potential counterexample is genuine or spurious, but
blanchet@33191
  1910
their potential for clutter is real.
blanchet@33191
  1911
blanchet@33191
  1912
\opfalse{show\_consts}{hide\_consts}
blanchet@33191
  1913
Specifies whether the values of constants occurring in the formula (including
blanchet@33191
  1914
its axioms) should be displayed along with any counterexample. These values are
blanchet@33191
  1915
sometimes helpful when investigating why a counterexample is
blanchet@33191
  1916
genuine, but they can clutter the output.
blanchet@33191
  1917
blanchet@33191
  1918
\opfalse{show\_all}{dont\_show\_all}
blanchet@33191
  1919
Enabling this option effectively enables \textit{show\_skolems},
blanchet@33191
  1920
\textit{show\_datatypes}, and \textit{show\_consts}.
blanchet@33191
  1921
blanchet@33191
  1922
\opt{max\_potential}{int}{$\mathbf{1}$}
blanchet@33191
  1923
Specifies the maximum number of potential counterexamples to display. Setting
blanchet@33191
  1924
this option to 0 speeds up the search for a genuine counterexample. This option
blanchet@33191
  1925
is implicitly set to 0 for automatic runs. If you set this option to a value
blanchet@33191
  1926
greater than 1, you will need an incremental SAT solver: For efficiency, it is
blanchet@33191
  1927
recommended to install the JNI version of MiniSat and set \textit{sat\_solver} =
blanchet@33191
  1928
\textit{MiniSatJNI}. Also be aware that many of the counterexamples may look
blanchet@33191
  1929
identical, unless the \textit{show\_all} (\S\ref{output-format}) option is
blanchet@33191
  1930
enabled.
blanchet@33191
  1931
blanchet@33191
  1932
\nopagebreak
blanchet@33561
  1933
{\small See also \textit{check\_potential} (\S\ref{authentication}) and
blanchet@33191
  1934
\textit{sat\_solver} (\S\ref{optimizations}).}
blanchet@33191
  1935
blanchet@33191
  1936
\opt{max\_genuine}{int}{$\mathbf{1}$}
blanchet@33191
  1937
Specifies the maximum number of genuine counterexamples to display. If you set
blanchet@33191
  1938
this option to a value greater than 1, you will need an incremental SAT solver:
blanchet@33191
  1939
For efficiency, it is recommended to install the JNI version of MiniSat and set
blanchet@33191
  1940
\textit{sat\_solver} = \textit{MiniSatJNI}. Also be aware that many of the
blanchet@33191
  1941
counterexamples may look identical, unless the \textit{show\_all}
blanchet@33191
  1942
(\S\ref{output-format}) option is enabled.
blanchet@33191
  1943
blanchet@33191
  1944
\nopagebreak
blanchet@33191
  1945
{\small See also \textit{check\_genuine} (\S\ref{authentication}) and
blanchet@33191
  1946
\textit{sat\_solver} (\S\ref{optimizations}).}
blanchet@33191
  1947
blanchet@33191
  1948
\ops{eval}{term\_list}
blanchet@33191
  1949
Specifies the list of terms whose values should be displayed along with
blanchet@33191
  1950
counterexamples. This option suffers from an ``observer effect'': Nitpick might
blanchet@33191
  1951
find different counterexamples for different values of this option.
blanchet@33191
  1952
blanchet@33191
  1953
\opu{format}{term}{int\_seq}
blanchet@33191
  1954
Specifies how to uncurry the value displayed for a variable or constant.
blanchet@33191
  1955
Uncurrying sometimes increases the readability of the output for high-arity
blanchet@33191
  1956
functions. For example, given the variable $y \mathbin{\Colon} {'a}\Rightarrow
blanchet@33191
  1957
{'b}\Rightarrow {'c}\Rightarrow {'d}\Rightarrow {'e}\Rightarrow {'f}\Rightarrow
blanchet@33191
  1958
{'g}$, setting \textit{format}~$y$ = 3 tells Nitpick to group the last three
blanchet@33191
  1959
arguments, as if the type had been ${'a}\Rightarrow {'b}\Rightarrow
blanchet@33191
  1960
{'c}\Rightarrow {'d}\times {'e}\times {'f}\Rightarrow {'g}$. In general, a list
blanchet@33191
  1961
of values $n_1,\ldots,n_k$ tells Nitpick to show the last $n_k$ arguments as an
blanchet@33191
  1962
$n_k$-tuple, the previous $n_{k-1}$ arguments as an $n_{k-1}$-tuple, and so on;
blanchet@33191
  1963
arguments that are not accounted for are left alone, as if the specification had
blanchet@33191
  1964
been $1,\ldots,1,n_1,\ldots,n_k$.
blanchet@33191
  1965
blanchet@33191
  1966
\nopagebreak
blanchet@33191
  1967
{\small See also \textit{uncurry} (\S\ref{optimizations}).}
blanchet@33191
  1968
blanchet@33191
  1969
\opt{format}{int\_seq}{$\mathbf{1}$}
blanchet@33191
  1970
Specifies the default format to use. Irrespective of the default format, the
blanchet@33191
  1971
extra arguments to a Skolem constant corresponding to the outer bound variables
blanchet@33191
  1972
are kept separated from the remaining arguments, the \textbf{for} arguments of
blanchet@33191
  1973
an inductive definitions are kept separated from the remaining arguments, and
blanchet@33191
  1974
the iteration counter of an unrolled inductive definition is shown alone. The
blanchet@33191
  1975
default format can be overridden on a per-variable or per-constant basis using
blanchet@33191
  1976
the \textit{format}~\qty{term} option described above.
blanchet@33191
  1977
\end{enum}
blanchet@33191
  1978
blanchet@33191
  1979
%% MARK: Authentication
blanchet@33191
  1980
\subsection{Authentication}
blanchet@33191
  1981
\label{authentication}
blanchet@33191
  1982
blanchet@33191
  1983
\begin{enum}
blanchet@33191
  1984
\opfalse{check\_potential}{trust\_potential}
blanchet@33191
  1985
Specifies whether potential counterexamples should be given to Isabelle's
blanchet@33191
  1986
\textit{auto} tactic to assess their validity. If a potential counterexample is
blanchet@33191
  1987
shown to be genuine, Nitpick displays a message to this effect and terminates.
blanchet@33191
  1988
blanchet@33191
  1989
\nopagebreak
blanchet@33561
  1990
{\small See also \textit{max\_potential} (\S\ref{output-format}).}
blanchet@33191
  1991
blanchet@33191
  1992
\opfalse{check\_genuine}{trust\_genuine}
blanchet@33191
  1993
Specifies whether genuine and likely genuine counterexamples should be given to
blanchet@33191
  1994
Isabelle's \textit{auto} tactic to assess their validity. If a ``genuine''
blanchet@33191
  1995
counterexample is shown to be spurious, the user is kindly asked to send a bug
blanchet@33191
  1996
report to the author at
blanchet@33191
  1997
\texttt{blan{\color{white}nospam}\kern-\wd\boxA{}chette@in.tum.de}.
blanchet@33191
  1998
blanchet@33191
  1999
\nopagebreak
blanchet@33561
  2000
{\small See also \textit{max\_genuine} (\S\ref{output-format}).}
blanchet@33191
  2001
blanchet@33191
  2002
\ops{expect}{string}
blanchet@33191
  2003
Specifies the expected outcome, which must be one of the following:
blanchet@33191
  2004
blanchet@33191
  2005
\begin{enum}
blanchet@33191
  2006
\item[$\bullet$] \textbf{\textit{genuine}}: Nitpick found a genuine counterexample.
blanchet@33191
  2007
\item[$\bullet$] \textbf{\textit{likely\_genuine}}: Nitpick found a ``likely
blanchet@33191
  2008
genuine'' counterexample (i.e., a counterexample that is genuine unless
blanchet@33191
  2009
it contradicts a missing axiom or a dangerous option was used inappropriately).
blanchet@33191
  2010
\item[$\bullet$] \textbf{\textit{potential}}: Nitpick found a potential counterexample.
blanchet@33191
  2011
\item[$\bullet$] \textbf{\textit{none}}: Nitpick found no counterexample.
blanchet@33191
  2012
\item[$\bullet$] \textbf{\textit{unknown}}: Nitpick encountered some problem (e.g.,
blanchet@33191
  2013
Kodkod ran out of memory).
blanchet@33191
  2014
\end{enum}
blanchet@33191
  2015
blanchet@33191
  2016
Nitpick emits an error if the actual outcome differs from the expected outcome.
blanchet@33191
  2017
This option is useful for regression testing.
blanchet@33191
  2018
\end{enum}
blanchet@33191
  2019
blanchet@33191
  2020
\subsection{Optimizations}
blanchet@33191
  2021
\label{optimizations}
blanchet@33191
  2022
blanchet@33191
  2023
\def\cpp{C\nobreak\raisebox{.1ex}{+}\nobreak\raisebox{.1ex}{+}}
blanchet@33191
  2024
blanchet@33191
  2025
\sloppy
blanchet@33191
  2026
blanchet@33191
  2027
\begin{enum}
blanchet@33191
  2028
\opt{sat\_solver}{string}{smart}
blanchet@33191
  2029
Specifies which SAT solver to use. SAT solvers implemented in C or \cpp{} tend
blanchet@33191
  2030
to be faster than their Java counterparts, but they can be more difficult to
blanchet@33191
  2031
install. Also, if you set the \textit{max\_potential} (\S\ref{output-format}) or
blanchet@33191
  2032
\textit{max\_genuine} (\S\ref{output-format}) option to a value greater than 1,
blanchet@33191
  2033
you will need an incremental SAT solver, such as \textit{MiniSatJNI}
blanchet@33191
  2034
(recommended) or \textit{SAT4J}.
blanchet@33191
  2035
blanchet@33191
  2036
The supported solvers are listed below:
blanchet@33191
  2037
blanchet@33191
  2038
\begin{enum}
blanchet@33191
  2039
blanchet@33191
  2040
\item[$\bullet$] \textbf{\textit{MiniSat}}: MiniSat is an efficient solver
blanchet@33191
  2041
written in \cpp{}. To use MiniSat, set the environment variable
blanchet@33191
  2042
\texttt{MINISAT\_HOME} to the directory that contains the \texttt{minisat}
blanchet@33191
  2043
executable. The \cpp{} sources and executables for MiniSat are available at
blanchet@33191
  2044
\url{http://minisat.se/MiniSat.html}. Nitpick has been tested with versions 1.14
blanchet@33191
  2045
and 2.0 beta (2007-07-21).
blanchet@33191
  2046
blanchet@33191
  2047
\item[$\bullet$] \textbf{\textit{MiniSatJNI}}: The JNI (Java Native Interface)
blanchet@33191
  2048
version of MiniSat is bundled in \texttt{nativesolver.\allowbreak tgz}, which
blanchet@33191
  2049
you will find on Kodkod's web site \cite{kodkod-2009}. Unlike the standard
blanchet@33191
  2050
version of MiniSat, the JNI version can be used incrementally.
blanchet@33191
  2051
blanchet@33731
  2052
%%% No longer true:
blanchet@33731
  2053
%%% "It is bundled with Kodkodi and requires no further installation or
blanchet@33731
  2054
%%% configuration steps. Alternatively,"
blanchet@33191
  2055
\item[$\bullet$] \textbf{\textit{PicoSAT}}: PicoSAT is an efficient solver
blanchet@33731
  2056
written in C. You can install a standard version of
blanchet@33191
  2057
PicoSAT and set the environment variable \texttt{PICOSAT\_HOME} to the directory
blanchet@33191
  2058
that contains the \texttt{picosat} executable. The C sources for PicoSAT are
blanchet@33191
  2059
available at \url{http://fmv.jku.at/picosat/} and are also bundled with Kodkodi.
blanchet@33191
  2060
Nitpick has been tested with version 913.
blanchet@33191
  2061
blanchet@33191
  2062
\item[$\bullet$] \textbf{\textit{zChaff}}: zChaff is an efficient solver written
blanchet@33191
  2063
in \cpp{}. To use zChaff, set the environment variable \texttt{ZCHAFF\_HOME} to
blanchet@33191
  2064
the directory that contains the \texttt{zchaff} executable. The \cpp{} sources
blanchet@33191
  2065
and executables for zChaff are available at
blanchet@33191
  2066
\url{http://www.princeton.edu/~chaff/zchaff.html}. Nitpick has been tested with
blanchet@33191
  2067
versions 2004-05-13, 2004-11-15, and 2007-03-12.
blanchet@33191
  2068
blanchet@33191
  2069
\item[$\bullet$] \textbf{\textit{zChaffJNI}}: The JNI version of zChaff is
blanchet@33191
  2070
bundled in \texttt{native\-solver.\allowbreak tgz}, which you will find on
blanchet@33191
  2071
Kodkod's web site \cite{kodkod-2009}.
blanchet@33191
  2072
blanchet@33191
  2073
\item[$\bullet$] \textbf{\textit{RSat}}: RSat is an efficient solver written in
blanchet@33191
  2074
\cpp{}. To use RSat, set the environment variable \texttt{RSAT\_HOME} to the
blanchet@33191
  2075
directory that contains the \texttt{rsat} executable. The \cpp{} sources for
blanchet@33191
  2076
RSat are available at \url{http://reasoning.cs.ucla.edu/rsat/}. Nitpick has been
blanchet@33191
  2077
tested with version 2.01.
blanchet@33191
  2078
blanchet@33191
  2079
\item[$\bullet$] \textbf{\textit{BerkMin}}: BerkMin561 is an efficient solver
blanchet@33191
  2080
written in C. To use BerkMin, set the environment variable
blanchet@33191
  2081
\texttt{BERKMIN\_HOME} to the directory that contains the \texttt{BerkMin561}
blanchet@33191
  2082
executable. The BerkMin executables are available at
blanchet@33191
  2083
\url{http://eigold.tripod.com/BerkMin.html}.
blanchet@33191
  2084
blanchet@33191
  2085
\item[$\bullet$] \textbf{\textit{BerkMinAlloy}}: Variant of BerkMin that is
blanchet@33191
  2086
included with Alloy 4 and calls itself ``sat56'' in its banner text. To use this
blanchet@33191
  2087
version of BerkMin, set the environment variable
blanchet@33191
  2088
\texttt{BERKMINALLOY\_HOME} to the directory that contains the \texttt{berkmin}
blanchet@33191
  2089
executable.
blanchet@33191
  2090
blanchet@33191
  2091
\item[$\bullet$] \textbf{\textit{Jerusat}}: Jerusat 1.3 is an efficient solver
blanchet@33191
  2092
written in C. To use Jerusat, set the environment variable
blanchet@33191
  2093
\texttt{JERUSAT\_HOME} to the directory that contains the \texttt{Jerusat1.3}
blanchet@33191
  2094
executable. The C sources for Jerusat are available at
blanchet@33191
  2095
\url{http://www.cs.tau.ac.il/~ale1/Jerusat1.3.tgz}.
blanchet@33191
  2096
blanchet@33191
  2097
\item[$\bullet$] \textbf{\textit{SAT4J}}: SAT4J is a reasonably efficient solver
blanchet@33191
  2098
written in Java that can be used incrementally. It is bundled with Kodkodi and
blanchet@33191
  2099
requires no further installation or configuration steps. Do not attempt to
blanchet@33191
  2100
install the official SAT4J packages, because their API is incompatible with
blanchet@33191
  2101
Kodkod.
blanchet@33191
  2102
blanchet@33191
  2103
\item[$\bullet$] \textbf{\textit{SAT4JLight}}: Variant of SAT4J that is
blanchet@33191
  2104
optimized for small problems. It can also be used incrementally.
blanchet@33191
  2105
blanchet@33191
  2106
\item[$\bullet$] \textbf{\textit{HaifaSat}}: HaifaSat 1.0 beta is an
blanchet@33191
  2107
experimental solver written in \cpp. To use HaifaSat, set the environment
blanchet@33191
  2108
variable \texttt{HAIFASAT\_\allowbreak HOME} to the directory that contains the
blanchet@33191
  2109
\texttt{HaifaSat} executable. The \cpp{} sources for HaifaSat are available at
blanchet@33191
  2110
\url{http://cs.technion.ac.il/~gershman/HaifaSat.htm}.
blanchet@33191
  2111
blanchet@33191
  2112
\item[$\bullet$] \textbf{\textit{smart}}: If \textit{sat\_solver} is set to
blanchet@33731
  2113
\textit{smart}, Nitpick selects the first solver among MiniSat,
blanchet@33731
  2114
PicoSAT, zChaff, RSat, BerkMin, BerkMinAlloy, Jerusat, MiniSatJNI, and zChaffJNI
blanchet@33731
  2115
that is recognized by Isabelle. If none is found, it falls back on SAT4J, which
blanchet@33731
  2116
should always be available. If \textit{verbose} (\S\ref{output-format}) is
blanchet@33731
  2117
enabled, Nitpick displays which SAT solver was chosen.
blanchet@33191
  2118
\end{enum}
blanchet@33191
  2119
\fussy
blanchet@33191
  2120
blanchet@33191
  2121
\opt{batch\_size}{int\_or\_smart}{smart}
blanchet@33191
  2122
Specifies the maximum number of Kodkod problems that should be lumped together
blanchet@33191
  2123
when invoking Kodkodi. Each problem corresponds to one scope. Lumping problems
blanchet@33191
  2124
together ensures that Kodkodi is launched less often, but it makes the verbose
blanchet@33191
  2125
output less readable and is sometimes detrimental to performance. If
blanchet@33191
  2126
\textit{batch\_size} is set to \textit{smart}, the actual value used is 1 if
blanchet@33191
  2127
\textit{debug} (\S\ref{output-format}) is set and 64 otherwise.
blanchet@33191
  2128
blanchet@33191
  2129
\optrue{destroy\_constrs}{dont\_destroy\_constrs}
blanchet@33191
  2130
Specifies whether formulas involving (co)in\-duc\-tive datatype constructors should
blanchet@33191
  2131
be rewritten to use (automatically generated) discriminators and destructors.
blanchet@33191
  2132
This optimization can drastically reduce the size of the Boolean formulas given
blanchet@33191
  2133
to the SAT solver.
blanchet@33191
  2134
blanchet@33191
  2135
\nopagebreak
blanchet@33191
  2136
{\small See also \textit{debug} (\S\ref{output-format}).}
blanchet@33191
  2137
blanchet@33191
  2138
\optrue{specialize}{dont\_specialize}
blanchet@33191
  2139
Specifies whether functions invoked with static arguments should be specialized.
blanchet@33191
  2140
This optimization can drastically reduce the search space, especially for
blanchet@33191
  2141
higher-order functions.
blanchet@33191
  2142
blanchet@33191
  2143
\nopagebreak
blanchet@33191
  2144
{\small See also \textit{debug} (\S\ref{output-format}) and
blanchet@33191
  2145
\textit{show\_consts} (\S\ref{output-format}).}
blanchet@33191
  2146
blanchet@33191
  2147
\optrue{skolemize}{dont\_skolemize}
blanchet@33191
  2148
Specifies whether the formula should be skolemized. For performance reasons,
blanchet@33191
  2149
(positive) $\forall$-quanti\-fiers that occur in the scope of a higher-order
blanchet@33191
  2150
(positive) $\exists$-quanti\-fier are left unchanged.
blanchet@33191
  2151
blanchet@33191
  2152
\nopagebreak
blanchet@33191
  2153
{\small See also \textit{debug} (\S\ref{output-format}) and
blanchet@33191
  2154
\textit{show\_skolems} (\S\ref{output-format}).}
blanchet@33191
  2155
blanchet@33191
  2156
\optrue{star\_linear\_preds}{dont\_star\_linear\_preds}
blanchet@33191
  2157
Specifies whether Nitpick should use Kodkod's transitive closure operator to
blanchet@33191
  2158
encode non-well-founded ``linear inductive predicates,'' i.e., inductive
blanchet@33191
  2159
predicates for which each the predicate occurs in at most one assumption of each
blanchet@33191
  2160
introduction rule. Using the reflexive transitive closure is in principle
blanchet@33191
  2161
equivalent to setting \textit{iter} to the cardinality of the predicate's
blanchet@33191
  2162
domain, but it is usually more efficient.
blanchet@33191
  2163
blanchet@33191
  2164
{\small See also \textit{wf} (\S\ref{scope-of-search}), \textit{debug}
blanchet@33191
  2165
(\S\ref{output-format}), and \textit{iter} (\S\ref{scope-of-search}).}
blanchet@33191
  2166
blanchet@33191
  2167
\optrue{uncurry}{dont\_uncurry}
blanchet@33191
  2168
Specifies whether Nitpick should uncurry functions. Uncurrying has on its own no
blanchet@33191
  2169
tangible effect on efficiency, but it creates opportunities for the boxing 
blanchet@33191
  2170
optimization.
blanchet@33191
  2171
blanchet@33191
  2172
\nopagebreak
blanchet@33191
  2173
{\small See also \textit{box} (\S\ref{scope-of-search}), \textit{debug}
blanchet@33191
  2174
(\S\ref{output-format}), and \textit{format} (\S\ref{output-format}).}
blanchet@33191
  2175
blanchet@33191
  2176
\optrue{fast\_descrs}{full\_descrs}
blanchet@33191
  2177
Specifies whether Nitpick should optimize the definite and indefinite
blanchet@33191
  2178
description operators (THE and SOME). The optimized versions usually help
blanchet@33191
  2179
Nitpick generate more counterexamples or at least find them faster, but only the
blanchet@33191
  2180
unoptimized versions are complete when all types occurring in the formula are
blanchet@33191
  2181
finite.
blanchet@33191
  2182
blanchet@33191
  2183
{\small See also \textit{debug} (\S\ref{output-format}).}
blanchet@33191
  2184
blanchet@33191
  2185
\optrue{peephole\_optim}{no\_peephole\_optim}
blanchet@33191
  2186
Specifies whether Nitpick should simplify the generated Kodkod formulas using a
blanchet@33191
  2187
peephole optimizer. These optimizations can make a significant difference.
blanchet@33191
  2188
Unless you are tracking down a bug in Nitpick or distrust the peephole
blanchet@33191
  2189
optimizer, you should leave this option enabled.
blanchet@33191
  2190
blanchet@33191
  2191
\opt{sym\_break}{int}{20}
blanchet@33191
  2192
Specifies an upper bound on the number of relations for which Kodkod generates
blanchet@33191
  2193
symmetry breaking predicates. According to the Kodkod documentation
blanchet@33191
  2194
\cite{kodkod-2009-options}, ``in general, the higher this value, the more
blanchet@33191
  2195
symmetries will be broken, and the faster the formula will be solved. But,
blanchet@33191
  2196
setting the value too high may have the opposite effect and slow down the
blanchet@33191
  2197
solving.''
blanchet@33191
  2198
blanchet@33191
  2199
\opt{sharing\_depth}{int}{3}
blanchet@33191
  2200
Specifies the depth to which Kodkod should check circuits for equivalence during
blanchet@33191
  2201
the translation to SAT. The default of 3 is the same as in Alloy. The minimum
blanchet@33191
  2202
allowed depth is 1. Increasing the sharing may result in a smaller SAT problem,
blanchet@33191
  2203
but can also slow down Kodkod.
blanchet@33191
  2204
blanchet@33191
  2205
\opfalse{flatten\_props}{dont\_flatten\_props}
blanchet@33191
  2206
Specifies whether Kodkod should try to eliminate intermediate Boolean variables.
blanchet@33191
  2207
Although this might sound like a good idea, in practice it can drastically slow
blanchet@33191
  2208
down Kodkod.
blanchet@33191
  2209
blanchet@33191
  2210
\opt{max\_threads}{int}{0}
blanchet@33191
  2211
Specifies the maximum number of threads to use in Kodkod. If this option is set
blanchet@33191
  2212
to 0, Kodkod will compute an appropriate value based on the number of processor
blanchet@33191
  2213
cores available.
blanchet@33191
  2214
blanchet@33191
  2215
\nopagebreak
blanchet@33191
  2216
{\small See also \textit{batch\_size} (\S\ref{optimizations}) and
blanchet@33191
  2217
\textit{timeout} (\S\ref{timeouts}).}
blanchet@33191
  2218
\end{enum}
blanchet@33191
  2219
blanchet@33191
  2220
\subsection{Timeouts}
blanchet@33191
  2221
\label{timeouts}
blanchet@33191
  2222
blanchet@33191
  2223
\begin{enum}
blanchet@33191
  2224
\opt{timeout}{time}{$\mathbf{30}$ s}
blanchet@33191
  2225
Specifies the maximum amount of time that the \textbf{nitpick} command should
blanchet@33191
  2226
spend looking for a counterexample. Nitpick tries to honor this constraint as
blanchet@33191
  2227
well as it can but offers no guarantees. For automatic runs,
blanchet@33561
  2228
\textit{timeout} is ignored; instead, Auto Quickcheck and Auto Nitpick share
blanchet@33561
  2229
a time slot whose length is specified by the ``Auto Counterexample Time
blanchet@33561
  2230
Limit'' option in Proof General.
blanchet@33191
  2231
blanchet@33191
  2232
\nopagebreak
blanchet@33561
  2233
{\small See also \textit{max\_threads} (\S\ref{optimizations}).}
blanchet@33191
  2234
blanchet@33556
  2235
\opt{tac\_timeout}{time}{$\mathbf{500}$\,ms}
blanchet@33191
  2236
Specifies the maximum amount of time that the \textit{auto} tactic should use
blanchet@33191
  2237
when checking a counterexample, and similarly that \textit{lexicographic\_order}
blanchet@33191
  2238
and \textit{sizechange} should use when checking whether a (co)in\-duc\-tive
blanchet@33191
  2239
predicate is well-founded. Nitpick tries to honor this constraint as well as it
blanchet@33191
  2240
can but offers no guarantees.
blanchet@33191
  2241
blanchet@33191
  2242
\nopagebreak
blanchet@33191
  2243
{\small See also \textit{wf} (\S\ref{scope-of-search}),
blanchet@33191
  2244
\textit{check\_potential} (\S\ref{authentication}),
blanchet@33191
  2245
and \textit{check\_genuine} (\S\ref{authentication}).}
blanchet@33191
  2246
\end{enum}
blanchet@33191
  2247
blanchet@33191
  2248
\section{Attribute Reference}
blanchet@33191
  2249
\label{attribute-reference}
blanchet@33191
  2250
blanchet@33191
  2251
Nitpick needs to consider the definitions of all constants occurring in a
blanchet@33191
  2252
formula in order to falsify it. For constants introduced using the
blanchet@33191
  2253
\textbf{definition} command, the definition is simply the associated
blanchet@33191
  2254
\textit{\_def} axiom. In contrast, instead of using the internal representation
blanchet@33191
  2255
of functions synthesized by Isabelle's \textbf{primrec}, \textbf{function}, and
blanchet@33191
  2256
\textbf{nominal\_primrec} packages, Nitpick relies on the more natural
blanchet@33191
  2257
equational specification entered by the user.
blanchet@33191
  2258
blanchet@33191
  2259
Behind the scenes, Isabelle's built-in packages and theories rely on the
blanchet@33191
  2260
following attributes to affect Nitpick's behavior:
blanchet@33191
  2261
blanchet@33191
  2262
\begin{itemize}
blanchet@33191
  2263
\flushitem{\textit{nitpick\_def}}
blanchet@33191
  2264
blanchet@33191
  2265
\nopagebreak
blanchet@33191
  2266
This attribute specifies an alternative definition of a constant. The
blanchet@33191
  2267
alternative definition should be logically equivalent to the constant's actual
blanchet@33191
  2268
axiomatic definition and should be of the form
blanchet@33191
  2269
blanchet@33191
  2270
\qquad $c~{?}x_1~\ldots~{?}x_n \,\equiv\, t$,
blanchet@33191
  2271
blanchet@33191
  2272
where ${?}x_1, \ldots, {?}x_n$ are distinct variables and $c$ does not occur in
blanchet@33191
  2273
$t$.
blanchet@33191
  2274
blanchet@33191
  2275
\flushitem{\textit{nitpick\_simp}}
blanchet@33191
  2276
blanchet@33191
  2277
\nopagebreak
blanchet@33191
  2278
This attribute specifies the equations that constitute the specification of a
blanchet@33191
  2279
constant. For functions defined using the \textbf{primrec}, \textbf{function},
blanchet@33191
  2280
and \textbf{nominal\_\allowbreak primrec} packages, this corresponds to the
blanchet@33191
  2281
\textit{simps} rules. The equations must be of the form
blanchet@33191
  2282
blanchet@33191
  2283
\qquad $c~t_1~\ldots\ t_n \,=\, u.$
blanchet@33191
  2284
blanchet@33191
  2285
\flushitem{\textit{nitpick\_psimp}}
blanchet@33191
  2286
blanchet@33191
  2287
\nopagebreak
blanchet@33191
  2288
This attribute specifies the equations that constitute the partial specification
blanchet@33191
  2289
of a constant. For functions defined using the \textbf{function} package, this
blanchet@33191
  2290
corresponds to the \textit{psimps} rules. The conditional equations must be of
blanchet@33191
  2291
the form
blanchet@33191
  2292
blanchet@33191
  2293
\qquad $\lbrakk P_1;\> \ldots;\> P_m\rbrakk \,\Longrightarrow\, c\ t_1\ \ldots\ t_n \,=\, u$.
blanchet@33191
  2294
blanchet@33191
  2295
\flushitem{\textit{nitpick\_intro}}
blanchet@33191
  2296
blanchet@33191
  2297
\nopagebreak
blanchet@33191
  2298
This attribute specifies the introduction rules of a (co)in\-duc\-tive predicate.
blanchet@33191
  2299
For predicates defined using the \textbf{inductive} or \textbf{coinductive}
blanchet@33191
  2300
command, this corresponds to the \textit{intros} rules. The introduction rules
blanchet@33191
  2301
must be of the form
blanchet@33191
  2302
blanchet@33191
  2303
\qquad $\lbrakk P_1;\> \ldots;\> P_m;\> M~(c\ t_{11}\ \ldots\ t_{1n});\>
blanchet@33191
  2304
\ldots;\> M~(c\ t_{k1}\ \ldots\ t_{kn})\rbrakk \,\Longrightarrow\, c\ u_1\
blanchet@33191
  2305
\ldots\ u_n$,
blanchet@33191
  2306
blanchet@33191
  2307
where the $P_i$'s are side conditions that do not involve $c$ and $M$ is an
blanchet@33191
  2308
optional monotonic operator. The order of the assumptions is irrelevant.
blanchet@33191
  2309
blanchet@33191
  2310
\end{itemize}
blanchet@33191
  2311
blanchet@33191
  2312
When faced with a constant, Nitpick proceeds as follows:
blanchet@33191
  2313
blanchet@33191
  2314
\begin{enum}
blanchet@33191
  2315
\item[1.] If the \textit{nitpick\_simp} set associated with the constant
blanchet@33191
  2316
is not empty, Nitpick uses these rules as the specification of the constant.
blanchet@33191
  2317
blanchet@33191
  2318
\item[2.] Otherwise, if the \textit{nitpick\_psimp} set associated with
blanchet@33191
  2319
the constant is not empty, it uses these rules as the specification of the
blanchet@33191
  2320
constant.
blanchet@33191
  2321
blanchet@33191
  2322
\item[3.] Otherwise, it looks up the definition of the constant:
blanchet@33191
  2323
blanchet@33191
  2324
\begin{enum}
blanchet@33191
  2325
\item[1.] If the \textit{nitpick\_def} set associated with the constant
blanchet@33191
  2326
is not empty, it uses the latest rule added to the set as the definition of the
blanchet@33191
  2327
constant; otherwise it uses the actual definition axiom.
blanchet@33191
  2328
\item[2.] If the definition is of the form
blanchet@33191
  2329
blanchet@33191
  2330
\qquad $c~{?}x_1~\ldots~{?}x_m \,\equiv\, \lambda y_1~\ldots~y_n.\; \textit{lfp}~(\lambda f.\; t)$,
blanchet@33191
  2331
blanchet@33191
  2332
then Nitpick assumes that the definition was made using an inductive package and
blanchet@33191
  2333
based on the introduction rules marked with \textit{nitpick\_\allowbreak
blanchet@33191
  2334
ind\_\allowbreak intros} tries to determine whether the definition is
blanchet@33191
  2335
well-founded.
blanchet@33191
  2336
\end{enum}
blanchet@33191
  2337
\end{enum}
blanchet@33191
  2338
blanchet@33191
  2339
As an illustration, consider the inductive definition
blanchet@33191
  2340
blanchet@33191
  2341
\prew
blanchet@33191
  2342
\textbf{inductive}~\textit{odd}~\textbf{where} \\
blanchet@33191
  2343
``\textit{odd}~1'' $\,\mid$ \\
blanchet@33191
  2344
``\textit{odd}~$n\,\Longrightarrow\, \textit{odd}~(\textit{Suc}~(\textit{Suc}~n))$''
blanchet@33191
  2345
\postw
blanchet@33191
  2346
blanchet@33191
  2347
Isabelle automatically attaches the \textit{nitpick\_intro} attribute to
blanchet@33191
  2348
the above rules. Nitpick then uses the \textit{lfp}-based definition in
blanchet@33191
  2349
conjunction with these rules. To override this, we can specify an alternative
blanchet@33191
  2350
definition as follows:
blanchet@33191
  2351
blanchet@33191
  2352
\prew
blanchet@33191
  2353
\textbf{lemma} $\mathit{odd\_def}'$ [\textit{nitpick\_def}]: ``$\textit{odd}~n \,\equiv\, n~\textrm{mod}~2 = 1$''
blanchet@33191
  2354
\postw
blanchet@33191
  2355
blanchet@33191
  2356
Nitpick then expands all occurrences of $\mathit{odd}~n$ to $n~\textrm{mod}~2
blanchet@33191
  2357
= 1$. Alternatively, we can specify an equational specification of the constant:
blanchet@33191
  2358
blanchet@33191
  2359
\prew
blanchet@33191
  2360
\textbf{lemma} $\mathit{odd\_simp}'$ [\textit{nitpick\_simp}]: ``$\textit{odd}~n = (n~\textrm{mod}~2 = 1)$''
blanchet@33191
  2361
\postw
blanchet@33191
  2362
blanchet@33191
  2363
Such tweaks should be done with great care, because Nitpick will assume that the
blanchet@33191
  2364
constant is completely defined by its equational specification. For example, if
blanchet@33191
  2365
you make ``$\textit{odd}~(2 * k + 1)$'' a \textit{nitpick\_simp} rule and neglect to provide rules to handle the $2 * k$ case, Nitpick will define
blanchet@33191
  2366
$\textit{odd}~n$ arbitrarily for even values of $n$. The \textit{debug}
blanchet@33191
  2367
(\S\ref{output-format}) option is extremely useful to understand what is going
blanchet@33191
  2368
on when experimenting with \textit{nitpick\_} attributes.
blanchet@33191
  2369
blanchet@33191
  2370
\section{Standard ML Interface}
blanchet@33191
  2371
\label{standard-ml-interface}
blanchet@33191
  2372
blanchet@33191
  2373
Nitpick provides a rich Standard ML interface used mainly for internal purposes
blanchet@33191
  2374
and debugging. Among the most interesting functions exported by Nitpick are
blanchet@33191
  2375
those that let you invoke the tool programmatically and those that let you
blanchet@33191
  2376
register and unregister custom coinductive datatypes.
blanchet@33191
  2377
blanchet@33191
  2378
\subsection{Invocation of Nitpick}
blanchet@33191
  2379
\label{invocation-of-nitpick}
blanchet@33191
  2380
blanchet@33191
  2381
The \textit{Nitpick} structure offers the following functions for invoking your
blanchet@33191
  2382
favorite counterexample generator:
blanchet@33191
  2383
blanchet@33191
  2384
\prew
blanchet@33191
  2385
$\textbf{val}\,~\textit{pick\_nits\_in\_term} : \\
blanchet@33191
  2386
\hbox{}\quad\textit{Proof.state} \rightarrow \textit{params} \rightarrow \textit{bool} \rightarrow \textit{term~list} \rightarrow \textit{term} \\
blanchet@33191
  2387
\hbox{}\quad{\rightarrow}\; \textit{string} * \textit{Proof.state}$ \\
blanchet@33191
  2388
$\textbf{val}\,~\textit{pick\_nits\_in\_subgoal} : \\
blanchet@33191
  2389
\hbox{}\quad\textit{Proof.state} \rightarrow \textit{params} \rightarrow \textit{bool} \rightarrow \textit{int} \rightarrow \textit{string} * \textit{Proof.state}$
blanchet@33191
  2390
\postw
blanchet@33191
  2391
blanchet@33191
  2392
The return value is a new proof state paired with an outcome string
blanchet@33191
  2393
(``genuine'', ``likely\_genuine'', ``potential'', ``none'', or ``unknown''). The
blanchet@33191
  2394
\textit{params} type is a large record that lets you set Nitpick's options. The
blanchet@33191
  2395
current default options can be retrieved by calling the following function
blanchet@33232
  2396
defined in the \textit{Nitpick\_Isar} structure:
blanchet@33191
  2397
blanchet@33191
  2398
\prew
blanchet@33191
  2399
$\textbf{val}\,~\textit{default\_params} :\,
blanchet@33191
  2400
\textit{theory} \rightarrow (\textit{string} * \textit{string})~\textit{list} \rightarrow \textit{params}$
blanchet@33191
  2401
\postw
blanchet@33191
  2402
blanchet@33191
  2403
The second argument lets you override option values before they are parsed and
blanchet@33191
  2404
put into a \textit{params} record. Here is an example:
blanchet@33191
  2405
blanchet@33191
  2406
\prew
blanchet@33232
  2407
$\textbf{val}\,~\textit{params} = \textit{Nitpick\_Isar.default\_params}~\textit{thy}~[(\textrm{``}\textrm{timeout}\textrm{''},\, \textrm{``}\textrm{none}\textrm{''})]$ \\
blanchet@33191
  2408
$\textbf{val}\,~(\textit{outcome},\, \textit{state}') = \textit{Nitpick.pick\_nits\_in\_subgoal}~\begin{aligned}[t]
blanchet@33191
  2409
& \textit{state}~\textit{params}~\textit{false} \\[-2pt]
blanchet@33191
  2410
& \textit{subgoal}\end{aligned}$
blanchet@33191
  2411
\postw
blanchet@33191
  2412
blanchet@33557
  2413
\let\antiq=\textrm
blanchet@33557
  2414
blanchet@33191
  2415
\subsection{Registration of Coinductive Datatypes}
blanchet@33191
  2416
\label{registration-of-coinductive-datatypes}
blanchet@33191
  2417
blanchet@33191
  2418
If you have defined a custom coinductive datatype, you can tell Nitpick about
blanchet@33191
  2419
it, so that it can use an efficient Kodkod axiomatization similar to the one it
blanchet@33191
  2420
uses for lazy lists. The interface for registering and unregistering coinductive
blanchet@33191
  2421
datatypes consists of the following pair of functions defined in the
blanchet@33191
  2422
\textit{Nitpick} structure:
blanchet@33191
  2423
blanchet@33191
  2424
\prew
blanchet@33191
  2425
$\textbf{val}\,~\textit{register\_codatatype} :\,
blanchet@33191
  2426
\textit{typ} \rightarrow \textit{string} \rightarrow \textit{styp~list} \rightarrow \textit{theory} \rightarrow \textit{theory}$ \\
blanchet@33191
  2427
$\textbf{val}\,~\textit{unregister\_codatatype} :\,
blanchet@33191
  2428
\textit{typ} \rightarrow \textit{theory} \rightarrow \textit{theory}$
blanchet@33191
  2429
\postw
blanchet@33191
  2430
blanchet@33191
  2431
The type $'a~\textit{llist}$ of lazy lists is already registered; had it
blanchet@33191
  2432
not been, you could have told Nitpick about it by adding the following line
blanchet@33191
  2433
to your theory file:
blanchet@33191
  2434
blanchet@33191
  2435
\prew
blanchet@33191
  2436
$\textbf{setup}~\,\{{*}\,~\!\begin{aligned}[t]
blanchet@33191
  2437
& \textit{Nitpick.register\_codatatype} \\[-2pt]
blanchet@33191
  2438
& \qquad @\{\antiq{typ}~``\kern1pt'a~\textit{llist}\textrm{''}\}~@\{\antiq{const\_name}~ \textit{llist\_case}\} \\[-2pt] %% TYPESETTING
blanchet@33191
  2439
& \qquad (\textit{map}~\textit{dest\_Const}~[@\{\antiq{term}~\textit{LNil}\},\, @\{\antiq{term}~\textit{LCons}\}])\,\ {*}\}\end{aligned}$
blanchet@33191
  2440
\postw
blanchet@33191
  2441
blanchet@33191
  2442
The \textit{register\_codatatype} function takes a coinductive type, its case
blanchet@33191
  2443
function, and the list of its constructors. The case function must take its
blanchet@33191
  2444
arguments in the order that the constructors are listed. If no case function
blanchet@33191
  2445
with the correct signature is available, simply pass the empty string.
blanchet@33191
  2446
blanchet@33191
  2447
On the other hand, if your goal is to cripple Nitpick, add the following line to
blanchet@33191
  2448
your theory file and try to check a few conjectures about lazy lists:
blanchet@33191
  2449
blanchet@33191
  2450
\prew
blanchet@33191
  2451
$\textbf{setup}~\,\{{*}\,~\textit{Nitpick.unregister\_codatatype}~@\{\antiq{typ}~``
blanchet@33191
  2452
\kern1pt'a~\textit{list}\textrm{''}\}\ \,{*}\}$
blanchet@33191
  2453
\postw
blanchet@33191
  2454
blanchet@33581
  2455
Inductive datatypes can be registered as coinductive datatypes, given
blanchet@33581
  2456
appropriate coinductive constructors. However, doing so precludes
blanchet@33581
  2457
the use of the inductive constructors---Nitpick will generate an error if they
blanchet@33581
  2458
are needed.
blanchet@33581
  2459
blanchet@33191
  2460
\section{Known Bugs and Limitations}
blanchet@33191
  2461
\label{known-bugs-and-limitations}
blanchet@33191
  2462
blanchet@33191
  2463
Here are the known bugs and limitations in Nitpick at the time of writing:
blanchet@33191
  2464
blanchet@33191
  2465
\begin{enum}
blanchet@33191
  2466
\item[$\bullet$] Underspecified functions defined using the \textbf{primrec},
blanchet@33191
  2467
\textbf{function}, or \textbf{nominal\_\allowbreak primrec} packages can lead
blanchet@33191
  2468
Nitpick to generate spurious counterexamples for theorems that refer to values
blanchet@33191
  2469
for which the function is not defined. For example:
blanchet@33191
  2470
blanchet@33191
  2471
\prew
blanchet@33191
  2472
\textbf{primrec} \textit{prec} \textbf{where} \\
blanchet@33191
  2473
``$\textit{prec}~(\textit{Suc}~n) = n$'' \\[2\smallskipamount]
blanchet@33191
  2474
\textbf{lemma} ``$\textit{prec}~0 = \undef$'' \\
blanchet@33191
  2475
\textbf{nitpick} \\[2\smallskipamount]
blanchet@33191
  2476
\quad{\slshape Nitpick found a counterexample for \textit{card nat}~= 2: 
blanchet@33191
  2477
\nopagebreak
blanchet@33191
  2478
\\[2\smallskipamount]
blanchet@33191
  2479
\hbox{}\qquad Empty assignment} \nopagebreak\\[2\smallskipamount]
blanchet@33191
  2480
\textbf{by}~(\textit{auto simp}: \textit{prec\_def})
blanchet@33191
  2481
\postw
blanchet@33191
  2482
blanchet@33191
  2483
Such theorems are considered bad style because they rely on the internal
blanchet@33191
  2484
representation of functions synthesized by Isabelle, which is an implementation
blanchet@33191
  2485
detail.
blanchet@33191
  2486
blanchet@33559
  2487
\item[$\bullet$] Nitpick maintains a global cache of wellfoundedness conditions,
blanchet@33556
  2488
which can become invalid if you change the definition of an inductive predicate
blanchet@33556
  2489
that is registered in the cache. To clear the cache,
blanchet@33556
  2490
run Nitpick with the \textit{tac\_timeout} option set to a new value (e.g.,
blanchet@33556
  2491
501$\,\textit{ms}$).
blanchet@33556
  2492
blanchet@33191
  2493
\item[$\bullet$] Nitpick produces spurious counterexamples when invoked after a
blanchet@33191
  2494
\textbf{guess} command in a structured proof.
blanchet@33191
  2495
blanchet@33191
  2496
\item[$\bullet$] The \textit{nitpick\_} attributes and the
blanchet@33191
  2497
\textit{Nitpick.register\_} functions can cause havoc if used improperly.
blanchet@33191
  2498
blanchet@33579
  2499
\item[$\bullet$] Although this has never been observed, arbitrary theorem
blanchet@33581
  2500
morphisms could possibly confuse Nitpick, resulting in spurious counterexamples.
blanchet@33579
  2501
blanchet@33191
  2502
\item[$\bullet$] Local definitions are not supported and result in an error.
blanchet@33191
  2503
blanchet@33731
  2504
%\item[$\bullet$] All constants and types whose names start with
blanchet@33731
  2505
%\textit{Nitpick}{.} are reserved for internal use.
blanchet@33191
  2506
\end{enum}
blanchet@33191
  2507
blanchet@33191
  2508
\let\em=\sl
blanchet@33191
  2509
\bibliography{../manual}{}
blanchet@33191
  2510
\bibliographystyle{abbrv}
blanchet@33191
  2511
blanchet@33191
  2512
\end{document}