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