In this chapter, we begin a new direction that will continue for the rest of the course. Up to now most of our attention has been focused on various aspects of Coq itself, while from now on we'll mostly be using Coq to formalize other things. (We'll continue to pause from time to time to introduce a few additional aspects of Coq.) Our first case study is a simple imperative programming language called Imp, embodying a tiny core fragment of conventional mainstream languages such as C and Java. Here is a familiar mathematical function written in Imp. This chapter looks at how to define the syntax and semantics of Imp; the chapters that follow develop a theory of program equivalence and introduce Hoare Logic, a widely used logic for reasoning about imperative programs.

Sflib

A minor technical point: Instead of asking Coq to import our earlier definitions from chapter Logic, we import a small library called Sflib.v, containing just a few definitions and theorems from earlier chapters that we'll actually use in the rest of the course. This change should be nearly invisible, since most of what's missing from Sflib has identical definitions in the Coq standard library. The main reason for doing it is to tidy the global Coq environment so that, for example, it is easier to search for relevant theorems.

Arithmetic and Boolean Expressions

We'll present Imp in three parts: first a core language of arithmetic and boolean expressions, then an extension of these expressions with variables, and finally a language of commands including assignment, conditions, sequencing, and loops.

Syntax

These two definitions specify the abstract syntax of arithmetic and boolean expressions.

In this chapter, we'll elide the translation from the concrete syntax that a programmer would actually write to these abstract syntax trees — the process that, for example, would translate the string "1+2×3" to the AST APlus (ANum 1) (AMult (ANum 2) (ANum 3)). The optional chapter ImpParser develops a simple implementation of a lexical analyzer and parser that can perform this translation. You do not need to understand that file to understand this one, but if you haven't taken a course where these techniques are covered (e.g., a compilers course) you may want to skim it.

For comparison, here's a conventional BNF (Backus-Naur Form) grammar defining the same abstract syntax: Compared to the Coq version above...

• The BNF is more informal — for example, it gives some suggestions about the surface syntax of expressions (like the fact that the addition operation is written + and is an infix symbol) while leaving other aspects of lexical analysis and parsing (like the relative precedence of +, -, and ×) unspecified. Some additional information — and human intelligence — would be required to turn this description into a formal definition (when implementing a compiler, for example).
  The Coq version consistently omits all this information and concentrates on the abstract syntax only.
• On the other hand, the BNF version is lighter and easier to read. Its informality makes it flexible, which is a huge advantage in situations like discussions at the blackboard, where conveying general ideas is more important than getting every detail nailed down precisely.
  Indeed, there are dozens of BNF-like notations and people switch freely among them, usually without bothering to say which form of BNF they're using because there is no need to: a rough-and-ready informal understanding is all that's needed.

It's good to be comfortable with both sorts of notations: informal ones for communicating between humans and formal ones for carrying out implementations and proofs.

Evaluation

Evaluating an arithmetic expression produces a number.

Similarly, evaluating a boolean expression yields a boolean.

Optimization

We haven't defined very much yet, but we can already get some mileage out of the definitions. Suppose we define a function that takes an arithmetic expression and slightly simplifies it, changing every occurrence of 0+e (i.e., (APlus (ANum 0) e) into just e.

To make sure our optimization is doing the right thing we can test it on some examples and see if the output looks OK.

But if we want to be sure the optimization is correct — i.e., that evaluating an optimized expression gives the same result as the original — we should prove it.

Coq Automation

The repetition in this last proof is starting to be a little annoying. If either the language of arithmetic expressions or the optimization being proved sound were significantly more complex, it would begin to be a real problem. So far, we've been doing all our proofs using just a small handful of Coq's tactics and completely ignoring its powerful facilities for constructing parts of proofs automatically. This section introduces some of these facilities, and we will see more over the next several chapters. Getting used to them will take some energy — Coq's automation is a power tool — but it will allow us to scale up our efforts to more complex definitions and more interesting properties without becoming overwhelmed by boring, repetitive, low-level details.

Tacticals

Tacticals is Coq's term for tactics that take other tactics as arguments — "higher-order tactics," if you will.

The repeat Tactical

The repeat tactical takes another tactic and keeps applying this tactic until the tactic fails. Here is an example showing that 100 is even using repeat.

The repeat T tactic never fails; if the tactic T doesn't apply to the original goal, then repeat still succeeds without changing the original goal (it repeats zero times).

The repeat T tactic does not have any bound on the number of times it applies T. If T is a tactic that always succeeds then repeat T will loop forever (e.g. repeat simpl loops forever since simpl always succeeds). While Coq's term language is guaranteed to terminate, Coq's tactic language is not!

The try Tactical

If T is a tactic, then try T is a tactic that is just like T except that, if T fails, try T successfully does nothing at all (instead of failing).

Using try in a completely manual proof is a bit silly, but we'll see below that try is very useful for doing automated proofs in conjunction with the ; tactical.

The ; Tactical (Simple Form)

In its most commonly used form, the ; tactical takes two tactics as argument: T;T' first performs the tactic T and then performs the tactic T' on each subgoal generated by T. For example, consider the following trivial lemma:

We can simplify this proof using the ; tactical:

Using try and ; together, we can get rid of the repetition in the proof that was bothering us a little while ago.

Coq experts often use this "...; try... " idiom after a tactic like induction to take care of many similar cases all at once. Naturally, this practice has an analog in informal proofs. Here is an informal proof of this theorem that matches the structure of the formal one: Theorem: For all arithmetic expressions a, Proof: By induction on a. The AMinus and AMult cases follow directly from the IH. The remaining cases are as follows:

• Suppose a = ANum n for some n. We must show
    aeval (optimize_0plus (ANum n)) = aeval (ANum n).
  This is immediate from the definition of optimize_0plus.
• Suppose a = APlus a1 a2 for some a1 and a2. We must show
    aeval (optimize_0plus (APlus a1 a2))
  = aeval (APlus a1 a2).
  Consider the possible forms of a1. For most of them, optimize_0plus simply calls itself recursively for the subexpressions and rebuilds a new expression of the same form as a1; in these cases, the result follows directly from the IH.
  The interesting case is when a1 = ANum n for some n. If n = ANum 0, then
    optimize_0plus (APlus a1 a2) = optimize_0plus a2
  and the IH for a2 is exactly what we need. On the other hand, if n = S n' for some n', then again optimize_0plus simply calls itself recursively, and the result follows from the IH. ☐

This proof can still be improved: the first case (for a = ANum n) is very trivial — even more trivial than the cases that we said simply followed from the IH — yet we have chosen to write it out in full. It would be better and clearer to drop it and just say, at the top, "Most cases are either immediate or direct from the IH. The only interesting case is the one for APlus..." We can make the same improvement in our formal proof too. Here's how it looks:

The ; Tactical (General Form)

The ; tactical has a more general than the simple T;T' we've seen above, which is sometimes also useful. If T, T₁, ..., Tn are tactics, then is a tactic that first performs T and then performs T₁ on the first subgoal generated by T, performs T₂ on the second subgoal, etc. So T;T' is just special notation for the case when all of the Ti's are the same tactic; i.e. T;T' is just a shorthand for:

Defining New Tactic Notations

Coq also provides several ways of "programming" tactic scripts.

• The Tactic Notation idiom illustrated below gives a handy way to define "shorthand tactics" that bundle several tactics into a single command.
• For more sophisticated programming, Coq offers a small built-in programming language called Ltac with primitives that can examine and modify the proof state. The details are a bit too complicated to get into here (and it is generally agreed that Ltac is not the most beautiful part of Coq's design!), but they can be found in the reference manual, and there are many examples of Ltac definitions in the Coq standard library that you can use as examples.
• There is also an OCaml API, which can be used to build tactics that access Coq's internal structures at a lower level, but this is seldom worth the trouble for ordinary Coq users.

The Tactic Notation mechanism is the easiest to come to grips with, and it offers plenty of power for many purposes. Here's an example.

This defines a new tactical called simpl_and_try which takes one tactic c as an argument, and is defined to be equivalent to the tactic simpl; try c. For example, writing "simpl_and_try reflexivity." in a proof would be the same as writing "simpl; try reflexivity." The next subsection gives a more sophisticated use of this feature...

Bulletproofing Case Analyses

Being able to deal with most of the cases of an induction or destruct all at the same time is very convenient, but it can also be a little confusing. One problem that often comes up is that maintaining proofs written in this style can be difficult. For example, suppose that, later, we extended the definition of aexp with another constructor that also required a special argument. The above proof might break because Coq generated the subgoals for this constructor before the one for APlus, so that, at the point when we start working on the APlus case, Coq is actually expecting the argument for a completely different constructor. What we'd like is to get a sensible error message saying "I was expecting the AFoo case at this point, but the proof script is talking about APlus." Here's a nice trick (due to Aaron Bohannon) that smoothly achieves this.

(Case_aux implements the common functionality of Case, SCase, SSCase, etc. For example, Case "foo" is defined as Case_aux Case "foo".) For example, if a is a variable of type aexp, then doing will perform an induction on a (the same as if we had just typed induction a) and also add a Case tag to each subgoal generated by the induction, labeling which constructor it comes from. For example, here is yet another proof of optimize_0plus_sound, using aexp_cases:

Exercise: 3 stars (optimize_0plus_b)

Since the optimize_0plus tranformation doesn't change the value of aexps, we should be able to apply it to all the aexps that appear in a bexp without changing the bexp's value. Write a function which performs that transformation on bexps, and prove it is sound. Use the tacticals we've just seen to make the proof as elegant as possible.

☐

Exercise: 4 stars, optional (optimizer)

Design exercise: The optimization implemented by our optimize_0plus function is only one of many imaginable optimizations on arithmetic and boolean expressions. Write a more sophisticated optimizer and prove it correct. (* FILL IN HERE *)
☐

The omega Tactic

The omega tactic implements a decision procedure for a subset of first-order logic called Presburger arithmetic. It is based on the Omega algorithm invented in 1992 by William Pugh. If the goal is a universally quantified formula made out of

• numeric constants, addition (+ and S), subtraction (- and pred), and multiplication by constants (this is what makes it Presburger arithmetic),
• equality (= and ≠) and inequality (≤), and
• the logical connectives ∧, ∨, ¬, and →,

then invoking omega will either solve the goal or tell you that it is actually false.

Liebniz wrote, "It is unworthy of excellent men to lose hours like slaves in the labor of calculation which could be relegated to anyone else if machines were used." We recommend using the omega tactic whenever possible.

A Few More Handy Tactics

Finally, here are some miscellaneous tactics that you may find convenient.

• clear H: Delete hypothesis H from the context.
• subst x: Find an assumption x = e or e = x in the context, replace x with e throughout the context and current goal, and clear the assumption.
• subst: Substitute away all assumptions of the form x = e or e = x.
• rename... into...: Change the name of a hypothesis in the proof context. For example, if the context includes a variable named x, then rename x into y will change all occurrences of x to y.
• assumption: Try to find a hypothesis H in the context that exactly matches the goal; if one is found, behave just like apply H.
• contradiction: Try to find a hypothesis H in the current context that is logically equivalent to False. If one is found, solve the goal.
• constructor: Try to find a constructor c (from some Inductive definition in the current environment) that can be applied to solve the current goal. If one is found, behave like apply c.

We'll see many examples of these in the proofs below.

Evaluation as a Relation

We have presented aeval and beval as functions defined by Fixpoints. Another way to think about evaluation — one that we will see is often more flexible — is as a relation between expressions and their values. This leads naturally to Inductive definitions like the following one for arithmetic expressions...

As is often the case with relations, we'll find it convenient to define infix notation for aevalR. We'll write e ⇓ n to mean that arithmetic expression e evaluates to value n. (This notation is one place where the limitation to ASCII symbols becomes a little bothersome. The standard notation for the evaluation relation is a double down-arrow. We'll typeset it like this in the HTML version of the notes and use a double vertical bar as the closest approximation in .v files.)

In fact, Coq provides a way to use this notation in the definition of aevalR itself. This avoids situations where we're working on a proof involving statements in the form e ⇓ n but we have to refer back to a definition written using the form aevalR e n. We do this by first "reserving" the notation, then giving the definition together with a declaration of what the notation means.

Inference Rule Notation

In informal discussions, it is convenient write the rules for aevalR and similar relations in the more readable graphical form of inference rules, where the premises above the line justify the conclusion below the line (we have already seen them in the Prop chapter). For example, the constructor E_APlus... ...would be written like this as an inference rule:

e1 ⇓ n1
e2 ⇓ n2	(E_APlus)
APlus e1 e2 ⇓ n1+n2

Formally, there is nothing very deep about inference rules: they are just implications. You can read the rule name on the right as the name of the constructor and read each of the linebreaks between the premises above the line and the line itself as →. All the variables mentioned in the rule (e1, n1, etc.) are implicitly bound by universal quantifiers at the beginning. (Such variables are often called metavariables to distinguish them from the variables of the language we are defining. At the moment, our arithmetic expressions don't include variables, but we'll soon be adding them.) The whole collection of rules is understood as being wrapped in an Inductive declaration (informally, this is either elided or else indicated by saying something like "Let aevalR be the smallest relation closed under the following rules..."). For example, ⇓ is the smallest relation closed under these rules:

	(E_ANum)
ANum n ⇓ n

e1 ⇓ n1
e2 ⇓ n2	(E_APlus)
APlus e1 e2 ⇓ n1+n2

e1 ⇓ n1
e2 ⇓ n2	(E_AMinus)
AMinus e1 e2 ⇓ n1-n2

e1 ⇓ n1
e2 ⇓ n2	(E_AMult)
AMult e1 e2 ⇓ n1*n2

Equivalence of the Definitions

It is straightforward to prove that the relational and functional definitions of evaluation agree on all possible arithmetic expressions...

Note: if you're reading the HTML file, you'll see an empty square box instead of a proof for this theorem. You can click on this box to "unfold" the text to see the proof. Click on the unfolded to text to "fold" it back up to a box. We'll be using this style frequently from now on to help keep the HTML easier to read. The full proofs always appear in the .v files. We can make the proof quite a bit shorter by making more use of tacticals...

Exercise: 3 stars (bevalR)

Write a relation bevalR in the same style as aevalR, and prove that it is equivalent to beval.

☐

Computational vs. Relational Definitions

For the definitions of evaluation for arithmetic and boolean expressions, the choice of whether to use functional or relational definitions is mainly a matter of taste. In general, Coq has somewhat better support for working with relations. On the other hand, in some sense function definitions carry more information, because functions are necessarily deterministic and defined on all arguments; for a relation we have to show these properties explicitly if we need them. Functions also take advantage of Coq's computations mechanism. However, there are circumstances where relational definitions of evaluation are preferable to functional ones.

For example, suppose that we wanted to extend the arithmetic operations by considering also a division operation:

Extending the definition of aeval to handle this new operation would not be straightforward (what should we return as the result of ADiv (ANum 5) (ANum 0)?). But extending aevalR is straightforward.

Adding nondeterminism

Suppose, instead, that we want to extend the arithmetic operations by a nondeterministic number generator any:

Again, extending aeval would be tricky (because evaluation is not a deterministic function from expressions to numbers), but extending aevalR is no problem:

Expressions With Variables

Let's turn our attention back to defining Imp. The next thing we need to do is to enrich our arithmetic and boolean expressions with variables. To keep things simple, we'll assume that all variables are global and that they only hold numbers.

Identifiers

To begin, we'll need to formalize identifiers such as program variables. We could use strings for this — or, in a real compiler, fancier structures like pointers into a symbol table. But for simplicity let's just use natural numbers as identifiers. (We hide this section in a module because these definitions are actually in SfLib, but we want to repeat them here so that we can explain them.)

We define a new inductive datatype Id so that we won't confuse identifiers and numbers. We use sumbool to define a computable equality operator on Id.

The following lemmas will be useful for rewriting terms involving eq_id_dec.

Exercise: 1 star, optional (neq_id)

☐

States

A state represents the current values of all the variables at some point in the execution of a program. For simplicity (to avoid dealing with partial functions), we let the state be defined for all variables, even though any given program is only going to mention a finite number of them. The state captures all of the information stored in memory. For Imp programs, because each variable stores only a natural number, we can represent the state as a mapping from identifiers to nat. For more complex programming languages, the state might have more structure.

For proofs involving states, we'll need several simple properties of update.

Exercise: 1 star (update_eq)

☐

Exercise: 1 star (update_neq)

☐

Exercise: 1 star (update_example)

Before starting to play with tactics, make sure you understand exactly what the theorem is saying!

☐

Exercise: 1 star (update_shadow)

☐

Exercise: 2 stars (update_same)

☐

Exercise: 3 stars (update_permute)

☐

Syntax

We can add variables to the arithmetic expressions we had before by simply adding one more constructor:

Defining a few variable names as notational shorthands will make examples easier to read:

(This convention for naming program variables (X, Y, Z) clashes a bit with our earlier use of uppercase letters for types. Since we're not using polymorphism heavily in this part of the course, this overloading should not cause confusion.) The definition of bexps is the same as before (using the new aexps):

Evaluation

The arith and boolean evaluators can be extended to handle variables in the obvious way:

Commands

Now we are ready define the syntax and behavior of Imp commands (often called statements).

Syntax

Informally, commands c are described by the following BNF grammar: For example, here's the factorial function in Imp. When this command terminates, the variable Y will contain the factorial of the initial value of X. Here is the formal definition of the syntax of commands:

As usual, we can use a few Notation declarations to make things more readable. We need to be a bit careful to avoid conflicts with Coq's built-in notations, so we'll keep this light — in particular, we won't introduce any notations for aexps and bexps to avoid confusion with the numerical and boolean operators we've already defined. We use the keyword IFB for conditionals instead of IF, for similar reasons.

For example, here is the factorial function again, written as a formal definition to Coq:

Examples

Assignment:

Loops

An infinite loop:

Evaluation

Next we need to define what it means to evaluate an Imp command. The fact that WHILE loops don't necessarily terminate makes defining an evaluation function tricky...

Evaluation as a Function (Failed Attempt)

Here's an attempt at defining an evaluation function for commands, omitting the WHILE case.

In a traditional functional programming language like ML or Haskell we could write the WHILE case as follows:

  Fixpoint ceval_fun (st : state) (c : com) : state :=
    match c with
      ...
      | WHILE b DO c END =>
          if (beval st b1)
            then ceval_fun st (c1; WHILE b DO c END)
            else st
    end.

Coq doesn't accept such a definition ("Error: Cannot guess decreasing argument of fix") because the function we want to define is not guaranteed to terminate. Indeed, it doesn't always terminate: for example, the full version of the ceval_fun function applied to the loop program above would never terminate. Since Coq is not just a functional programming language, but also a consistent logic, any potentially non-terminating function needs to be rejected. Here is an (invalid!) Coq program showing what would go wrong if Coq allowed non-terminating recursive functions:

     Fixpoint loop_false (n : nat) : False := loop_false n.

That is, propositions like False would become provable (e.g. loop_false 0 would be a proof of False), which would be a disaster for Coq's logical consistency. Thus, because it doesn't terminate on all inputs, the full version of ceval_fun cannot be written in Coq — at least not without additional tricks (see chapter ImpCEvalFun if curious).

Evaluation as a Relation

Here's a better way: we define ceval as a relation rather than a function — i.e., we define it in Prop instead of Type, as we did for aevalR above. This is an important change. Besides freeing us from the awkward workarounds that would be needed to define evaluation as a function, it gives us a lot more flexibility in the definition. For example, if we added concurrency features to the language, we'd want the definition of evaluation to be non-deterministic — i.e., not only would it not be total, it would not even be a partial function! We'll use the notation c / st ⇓ st' for our ceval relation: c / st ⇓ st' means that executing program c in a starting state st results in an ending state st'. This can be pronounced "c takes state st to st'".

Operational Semantics

	(E_Skip)
SKIP / st ⇓ st

aeval st a1 = n	(E_Ass)
x := a1 / st ⇓ (update st x n)

c1 / st ⇓ st'
c2 / st' ⇓ st''	(E_Seq)
c1;;c2 / st ⇓ st''

beval st b1 = true
c1 / st ⇓ st'	(E_IfTrue)
IF b1 THEN c1 ELSE c2 FI / st ⇓ st'

beval st b1 = false
c2 / st ⇓ st'	(E_IfFalse)
IF b1 THEN c1 ELSE c2 FI / st ⇓ st'

beval st b1 = false	(E_WhileEnd)
WHILE b DO c END / st ⇓ st

beval st b1 = true
c / st ⇓ st'
WHILE b DO c END / st' ⇓ st''	(E_WhileLoop)
WHILE b DO c END / st ⇓ st''

Here is the formal definition. (Make sure you understand how it corresponds to the inference rules.)

The cost of defining evaluation as a relation instead of a function is that we now need to construct proofs that some program evaluates to some result state, rather than just letting Coq's computation mechanism do it for us.

Exercise: 2 stars (ceval_example2)

☐

Exercise: 3 stars, advanced (pup_to_n)

Write an Imp program that sums the numbers from 1 to X (inclusive: 1 + 2 + ... + X) in the variable Y. Prove that this program executes as intended for X = 2 (this latter part is trickier than you might expect).

☐

Determinism of Evaluation

Changing from a computational to a relational definition of evaluation is a good move because it allows us to escape from the artificial requirement (imposed by Coq's restrictions on Fixpoint definitions) that evaluation should be a total function. But it also raises a question: Is the second definition of evaluation actually a partial function? That is, is it possible that, beginning from the same state st, we could evaluate some command c in different ways to reach two different output states st' and st''? In fact, this cannot happen: ceval is a partial function. Here's the proof:

Reasoning About Imp Programs

We'll get much deeper into systematic techniques for reasoning about Imp programs in the following chapters, but we can do quite a bit just working with the bare definitions.

Exercise: 3 stars (XtimesYinZ_spec)

State and prove a specification of XtimesYinZ.

☐

Exercise: 3 stars (loop_never_stops)

☐

Exercise: 3 stars (no_whilesR)

Consider the definition of the no_whiles property below:

This property yields true just on programs that have no while loops. Using Inductive, write a property no_whilesR such that no_whilesR c is provable exactly when c is a program with no while loops. Then prove its equivalence with no_whiles.

☐

Exercise: 4 stars (no_whiles_terminating)

Imp programs that don't involve while loops always terminate. State and prove a theorem that says this. (Use either no_whiles or no_whilesR, as you prefer.)

☐

Additional Exercises

Exercise: 3 stars (stack_compiler)

HP Calculators, programming languages like Forth and Postscript, and abstract machines like the Java Virtual Machine all evaluate arithmetic expressions using a stack. For instance, the expression

   (2*3)+(3*(4-2))

would be entered as

   2 3 * 3 4 2 - * +

and evaluated like this:

  []            |    2 3 * 3 4 2 - * +
  [2]           |    3 * 3 4 2 - * +
  [3, 2]        |    * 3 4 2 - * +
  [6]           |    3 4 2 - * +
  [3, 6]        |    4 2 - * +
  [4, 3, 6]     |    2 - * +
  [2, 4, 3, 6]  |    - * +
  [2, 3, 6]     |    * +
  [6, 6]        |    +
  [12]          |

The task of this exercise is to write a small compiler that translates aexps into stack machine instructions. The instruction set for our stack language will consist of the following instructions:

• SPush n: Push the number n on the stack.
• SLoad x: Load the identifier x from the store and push it on the stack
• SPlus: Pop the two top numbers from the stack, add them, and push the result onto the stack.
• SMinus: Similar, but subtract.
• SMult: Similar, but multiply.

Write a function to evaluate programs in the stack language. It takes as input a state, a stack represented as a list of numbers (top stack item is the head of the list), and a program represented as a list of instructions, and returns the stack after executing the program. Test your function on the examples below. Note that the specification leaves unspecified what to do when encountering an SPlus, SMinus, or SMult instruction if the stack contains less than two elements. In a sense, it is immaterial what we do, since our compiler will never emit such a malformed program.

Next, write a function which compiles an aexp into a stack machine program. The effect of running the program should be the same as pushing the value of the expression on the stack.

After you've defined s_compile, uncomment the following to test that it works.

☐

Exercise: 3 stars, advanced (stack_compiler_correct)

The task of this exercise is to prove the correctness of the calculator implemented in the previous exercise. Remember that the specification left unspecified what to do when encountering an SPlus, SMinus, or SMult instruction if the stack contains less than two elements. (In order to make your correctness proof easier you may find it useful to go back and change your implementation!) Prove the following theorem, stating that the compile function behaves correctly. You will need to start by stating a more general lemma to get a usable induction hypothesis; the main theorem will then be a simple corollary of this lemma.

☐

Exercise: 5 stars, advanced (break_imp)

Imperative languages such as C or Java often have a break or similar statement for interrupting the execution of loops. In this exercise we will consider how to add break to Imp. First, we need to enrich the language of commands with an additional case.

Next, we need to define the behavior of BREAK. Informally, whenever BREAK is executed in a sequence of commands, it stops the execution of that sequence and signals that the innermost enclosing loop (if any) should terminate. If there aren't any enclosing loops, then the whole program simply terminates. The final state should be the same as the one in which the BREAK statement was executed. One important point is what to do when there are multiple loops enclosing a given BREAK. In those cases, BREAK should only terminate the innermost loop where it occurs. Thus, after executing the following piece of code... ... the value of X should be 1, and not 0. One way of expressing this behavior is to add another parameter to the evaluation relation that specifies whether evaluation of a command executes a BREAK statement:

Intuitively, c / st ⇓ s / st' means that, if c is started in state st, then it terminates in state st' and either signals that any surrounding loop (or the whole program) should exit immediately (s = SBreak) or that execution should continue normally (s = SContinue). The definition of the "c / st ⇓ s / st'" relation is very similar to the one we gave above for the regular evaluation relation (c / st ⇓ s / st') — we just need to handle the termination signals appropriately:

• If the command is SKIP, then the state doesn't change, and execution of any enclosing loop can continue normally.
• If the command is BREAK, the state stays unchanged, but we signal a SBreak.
• If the command is an assignment, then we update the binding for that variable in the state accordingly and signal that execution can continue normally.
• If the command is of the form IF b THEN c1 ELSE c2 FI, then the state is updated as in the original semantics of Imp, except that we also propagate the signal from the execution of whichever branch was taken.
• If the command is a sequence c1 ; c2, we first execute c1. If this yields a SBreak, we skip the execution of c2 and propagate the SBreak signal to the surrounding context; the resulting state should be the same as the one obtained by executing c1 alone. Otherwise, we execute c2 on the state obtained after executing c1, and propagate the signal that was generated there.
• Finally, for a loop of the form WHILE b DO c END, the semantics is almost the same as before. The only difference is that, when b evaluates to true, we execute c and check the signal that it raises. If that signal is SContinue, then the execution proceeds as in the original semantics. Otherwise, we stop the execution of the loop, and the resulting state is the same as the one resulting from the execution of the current iteration. In either case, since BREAK only terminates the innermost loop, WHILE signals SContinue.

Based on the above description, complete the definition of the ceval relation.

Now the following properties of your definition of ceval:

Exercise: 3 stars, advanced, optional (while_break_true)

Exercise: 4 stars, advanced, optional (ceval_deterministic)

☐

Exercise: 3 stars, optional (short_circuit)

Most modern programming languages use a "short-circuit" evaluation rule for boolean and: to evaluate BAnd b1 b2, first evaluate b1. If it evaluates to false, then the entire BAnd expression evaluates to false immediately, without evaluating b2. Otherwise, b2 is evaluated to determine the result of the BAnd expression. Write an alternate version of beval that performs short-circuit evaluation of BAnd in this manner, and prove that it is equivalent to beval.

☐

Exercise: 4 stars, optional (add_for_loop)

Add C-style for loops to the language of commands, update the ceval definition to define the semantics of for loops, and add cases for for loops as needed so that all the proofs in this file are accepted by Coq. A for loop should be parameterized by (a) a statement executed initially, (b) a test that is run on each iteration of the loop to determine whether the loop should continue, (c) a statement executed at the end of each loop iteration, and (d) a statement that makes up the body of the loop. (You don't need to worry about making up a concrete Notation for for loops, but feel free to play with this too if you like.)

☐