-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathTypes.v
More file actions
818 lines (654 loc) · 27.3 KB
/
Types.v
File metadata and controls
818 lines (654 loc) · 27.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
(** * Types: Type Systems *)
(** Our next major topic is _type systems_ -- static program
analyses that classify expressions according to the "shapes" of
their results. We'll begin with a typed version of the simplest
imaginable language, to introduce the basic ideas of types and
typing rules and the fundamental theorems about type systems:
_type preservation_ and _progress_. In chapter [Stlc] we'll move
on to the _simply typed lambda-calculus_, which lives at the core
of every modern functional programming language (including
Coq!). *)
Set Warnings "-notation-overridden,-parsing,-deprecated-hint-without-locality".
From Coq Require Import Arith.
From PLF Require Import Maps.
From PLF Require Import Smallstep.
Set Default Goal Selector "!".
Hint Constructors multi : core.
(* ################################################################# *)
(** * Typed Arithmetic Expressions *)
(** To motivate the discussion of type systems, let's begin as
usual with a tiny toy language. We want it to have the potential
for programs to go wrong because of runtime type errors, so we
need something a tiny bit more complex than the language of
constants and addition that we used in chapter [Smallstep]: a
single kind of data (e.g., numbers) is too simple, but just two
kinds (numbers and booleans) gives us enough material to tell an
interesting story.
The language definition is completely routine. *)
(* ================================================================= *)
(** ** Syntax *)
(** Here is the syntax, informally:
t ::= true
| false
| if t then t else t
| 0
| succ t
| pred t
| iszero t
*)
(** And here it is formally: *)
Module TM.
Inductive tm : Type :=
| tru : tm
| fls : tm
| ite : tm -> tm -> tm -> tm
| zro : tm
| scc : tm -> tm
| prd : tm -> tm
| iszro : tm -> tm.
Declare Custom Entry tm.
Declare Scope tm_scope.
Notation "'true'" := true (at level 1): tm_scope.
Notation "'true'" := (tru) (in custom tm at level 0): tm_scope.
Notation "'false'" := false (at level 1): tm_scope.
Notation "'false'" := (fls) (in custom tm at level 0): tm_scope.
Notation "<{ e }>" := e (e custom tm at level 99): tm_scope.
Notation "( x )" := x (in custom tm, x at level 99): tm_scope.
Notation "x" := x (in custom tm at level 0, x constr at level 0): tm_scope.
Notation "'0'" := (zro) (in custom tm at level 0): tm_scope.
Notation "'0'" := 0 (at level 1): tm_scope.
Notation "'succ' x" := (scc x) (in custom tm at level 90, x custom tm at level 80): tm_scope.
Notation "'pred' x" := (prd x) (in custom tm at level 90, x custom tm at level 80): tm_scope.
Notation "'iszero' x" := (iszro x) (in custom tm at level 80, x custom tm at level 70): tm_scope.
Notation "'if' c 'then' t 'else' e" := (ite c t e)
(in custom tm at level 90, c custom tm at level 80,
t custom tm at level 80, e custom tm at level 80): tm_scope.
Local Open Scope tm_scope.
(** _Values_ are [true], [false], and numeric values... *)
Inductive bvalue : tm -> Prop :=
| bv_true : bvalue <{ true }>
| bv_false : bvalue <{ false }>.
Inductive nvalue : tm -> Prop :=
| nv_0 : nvalue <{ 0 }>
| nv_succ : forall t, nvalue t -> nvalue <{ succ t }>.
Definition value (t : tm) := bvalue t \/ nvalue t.
Hint Constructors bvalue nvalue : core.
Hint Unfold value : core.
(* ================================================================= *)
(** ** Operational Semantics *)
(** Here is the single-step relation, first informally...
------------------------------- (ST_IfTrue)
if true then t1 else t2 --> t1
------------------------------- (ST_IfFalse)
if false then t1 else t2 --> t2
t1 --> t1'
------------------------------------------------ (ST_If)
if t1 then t2 else t3 --> if t1' then t2 else t3
t1 --> t1'
-------------------- (ST_Succ)
succ t1 --> succ t1'
------------ (ST_Pred0)
pred 0 --> 0
numeric value v
------------------- (ST_PredSucc)
pred (succ v) --> v
t1 --> t1'
-------------------- (ST_Pred)
pred t1 --> pred t1'
----------------- (ST_IsZero0)
iszero 0 --> true
numeric value v
------------------------- (ST_IszeroSucc)
iszero (succ v) --> false
t1 --> t1'
------------------------ (ST_Iszero)
iszero t1 --> iszero t1'
*)
(** ... and then formally: *)
Reserved Notation "t '-->' t'" (at level 40).
Inductive step : tm -> tm -> Prop :=
| ST_IfTrue : forall t1 t2,
<{ if true then t1 else t2 }> --> t1
| ST_IfFalse : forall t1 t2,
<{ if false then t1 else t2 }> --> t2
| ST_If : forall c c' t2 t3,
c --> c' ->
<{ if c then t2 else t3 }> --> <{ if c' then t2 else t3 }>
| ST_Succ : forall t1 t1',
t1 --> t1' ->
<{ succ t1 }> --> <{ succ t1' }>
| ST_Pred0 :
<{ pred 0 }> --> <{ 0 }>
| ST_PredSucc : forall v,
nvalue v ->
<{ pred (succ v) }> --> v
| ST_Pred : forall t1 t1',
t1 --> t1' ->
<{ pred t1 }> --> <{ pred t1' }>
| ST_Iszero0 :
<{ iszero 0 }> --> <{ true }>
| ST_IszeroSucc : forall v,
nvalue v ->
<{ iszero (succ v) }> --> <{ false }>
| ST_Iszero : forall t1 t1',
t1 --> t1' ->
<{ iszero t1 }> --> <{ iszero t1' }>
where "t '-->' t'" := (step t t').
Hint Constructors step : core.
(** Notice that the [step] relation doesn't care about whether the
expression being stepped makes global sense -- it just checks that
the operation in the _next_ reduction step is being applied to the
right kinds of operands. For example, the term [succ true] cannot
take a step, but the almost as obviously nonsensical term
succ (if true then true else true)
can take a step (once, before becoming stuck). *)
(* ================================================================= *)
(** ** Normal Forms and Values *)
(** The first interesting thing to notice about this [step] relation
is that the strong progress theorem from the [Smallstep]
chapter fails here. That is, there are terms that are normal
forms (they can't take a step) but not values (they are not
included in our definition of possible "results of reduction").
Such terms are _stuck_. *)
Notation step_normal_form := (normal_form step).
Definition stuck (t : tm) : Prop :=
step_normal_form t /\ ~ value t.
Hint Unfold stuck : core.
(** **** Exercise: 2 stars, standard (some_term_is_stuck) *)
Example some_term_is_stuck :
exists t, stuck t.
Proof.
exists <{ pred true }>. split.
- intros contra. destruct contra as [t' contra].
inversion contra; subst. inversion H0.
- intros contra. inversion contra; inversion H.
Qed.
(** [] *)
(** However, although values and normal forms are _not_ the same in this
language, the set of values is a subset of the set of normal forms.
This is important because it shows we did not accidentally define
things so that some value could still take a step. *)
(** **** Exercise: 3 stars, standard (value_is_nf) *)
Lemma value_is_nf : forall t,
value t -> step_normal_form t.
Proof.
intros t Hv. inversion Hv.
- intros [t' contra]. inversion H; subst; inversion contra.
- induction H; intros [t' contra].
* inversion contra.
* assert (value t). { right. apply H. }
apply IHnvalue in H0. apply H0.
unfold step_normal_form in H0.
inversion contra; subst.
exists t1'. assumption.
Qed.
(** (Hint: You will reach a point in this proof where you need to
use an induction to reason about a term that is known to be a
numeric value. This induction can be performed either over the
term itself or over the evidence that it is a numeric value. The
proof goes through in either case, but you will find that one way
is quite a bit shorter than the other. For the sake of the
exercise, try to complete the proof both ways.)
[] *)
(** **** Exercise: 3 stars, standard, optional (step_deterministic)
Use [value_is_nf] to show that the [step] relation is also
deterministic. *)
Ltac step_inversion := match goal with
| H : ?a --> ?b |- _ => solve[ inversion H ]
end.
Ltac nvalue_contra := match goal with
| _ : nvalue ?v, H : _ --> _ |- _ => assert (Hv : value v) by (right; assumption);
apply value_is_nf in Hv; inversion H; subst;
assert (exists t', v --> t') by eauto;
contradiction
end.
Theorem step_deterministic:
deterministic step.
Proof with eauto.
unfold deterministic. intros x y1 y2 Hy1. generalize dependent y2.
induction Hy1; intros y2 Hy2; inversion Hy2; subst; try step_inversion; try nvalue_contra;
try (apply IHHy1 in H0; rewrite H0; reflexivity)...
- apply IHHy1 in H3. rewrite H3. reflexivity.
Qed.
(** [] *)
(* ================================================================= *)
(** ** Typing *)
(** The next critical observation is that, although this
language has stuck terms, they are always nonsensical, mixing
booleans and numbers in a way that we don't even _want_ to have a
meaning. We can easily exclude such ill-typed terms by defining a
_typing relation_ that relates terms to the types (either numeric
or boolean) of their final results. *)
Inductive ty : Type :=
| Bool : ty
| Nat : ty.
(** In informal notation, the typing relation is often written
[|-- t \in T] and pronounced "[t] has type [T]." The [|--] symbol
is called a "turnstile." Below, we're going to see richer typing
relations where one or more additional "context" arguments are
written to the left of the turnstile. For the moment, the context
is always empty.
----------------- (T_True)
|-- true \in Bool
------------------ (T_False)
|-- false \in Bool
|-- t1 \in Bool |-- t2 \in T |-- t3 \in T
----------------------------------------------- (T_If)
|-- if t1 then t2 else t3 \in T
-------------- (T_0)
|-- 0 \in Nat
|-- t1 \in Nat
------------------- (T_Succ)
|-- succ t1 \in Nat
|-- t1 \in Nat
------------------- (T_Pred)
|-- pred t1 \in Nat
|-- t1 \in Nat
---------------------- (T_Iszero)
|-- iszero t1 \in Bool
*)
Declare Custom Entry ty.
Notation "'Nat'" := Nat (in custom ty).
Notation "'Bool'" := Bool (in custom ty).
Notation "x" := x (in custom ty, x global).
Reserved Notation "<{ '|--' t '\in' T }>"
(at level 0, t custom tm, T custom ty).
Inductive has_type : tm -> ty -> Prop :=
| T_True :
<{ |-- true \in Bool }>
| T_False :
<{ |-- false \in Bool }>
| T_If : forall t1 t2 t3 T,
<{ |-- t1 \in Bool }> ->
<{ |-- t2 \in T }> ->
<{ |-- t3 \in T }> ->
<{ |-- if t1 then t2 else t3 \in T }>
| T_0 :
<{ |-- 0 \in Nat }>
| T_Succ : forall t1,
<{ |-- t1 \in Nat }> ->
<{ |-- succ t1 \in Nat }>
| T_Pred : forall t1,
<{ |-- t1 \in Nat }> ->
<{ |-- pred t1 \in Nat }>
| T_Iszero : forall t1,
<{ |-- t1 \in Nat }> ->
<{ |-- iszero t1 \in Bool }>
where "<{ '|--' t '\in' T }>" := (has_type t T).
Hint Constructors has_type : core.
Example has_type_1 :
<{ |-- if false then 0 else (succ 0) \in Nat }>.
Proof.
apply T_If.
- apply T_False.
- apply T_0.
- apply T_Succ. apply T_0.
Qed.
(** (Since we've included all the constructors of the typing relation
in the hint database, the [auto] tactic can actually find this
proof automatically.) *)
(** It's important to realize that the typing relation is a
_conservative_ (or _static_) approximation: it does not consider
what happens when the term is reduced -- in particular, it does
not calculate the type of its normal form. *)
Example has_type_not :
~ <{ |-- if false then 0 else true \in Bool }>.
Proof.
intros Contra. solve_by_inverts 2. Qed.
(** **** Exercise: 1 star, standard, optional (succ_hastype_nat__hastype_nat) *)
Example succ_hastype_nat__hastype_nat : forall t,
<{ |-- succ t \in Nat }> ->
<{ |-- t \in Nat }>.
Proof.
intros t Hs. inversion Hs. assumption.
Qed.
(** [] *)
(* ----------------------------------------------------------------- *)
(** *** Canonical forms *)
(** The following two lemmas capture the fundamental fact that the
definitions of boolean and numeric values agree with the typing
relation. *)
Lemma bool_canonical : forall t,
<{ |-- t \in Bool }> -> value t -> bvalue t.
Proof.
intros t HT [Hb | Hn].
- assumption.
- destruct Hn as [ | Hs].
+ inversion HT.
+ inversion HT.
Qed.
Lemma nat_canonical : forall t,
<{ |-- t \in Nat }> -> value t -> nvalue t.
Proof.
intros t HT [Hb | Hn].
- inversion Hb; subst; inversion HT.
- assumption.
Qed.
(* ================================================================= *)
(** ** Progress *)
(** The typing relation enjoys two critical properties.
The first is that well-typed normal forms are not stuck -- or
conversely, if a term is well typed, then either it is a value or it
can take at least one step. We call this _progress_. *)
(** **** Exercise: 3 stars, standard (finish_progress) *)
Theorem progress : forall t T,
<{ |-- t \in T }> ->
value t \/ exists t', t --> t'.
(** Complete the formal proof of the [progress] property. (Make sure
you understand the parts we've given of the informal proof in the
following exercise before starting -- this will save you a lot of
time.) *)
Proof.
intros t T HT.
induction HT; auto.
(* The cases that were obviously values, like T_True and
T_False, are eliminated immediately by auto *)
- (* T_If *)
right. destruct IHHT1.
+ (* t1 is a value *)
apply (bool_canonical t1 HT1) in H.
destruct H.
* exists t2. auto.
* exists t3. auto.
+ (* t1 can take a step *)
destruct H as [t1' H1].
exists <{ if t1' then t2 else t3 }>. auto.
- (* T_Succ *)
destruct IHHT as [IHHT | IHHT].
+ left. apply (nat_canonical t1 HT) in IHHT.
right. apply T_Succ in HT. apply nat_canonical; auto.
+ right. destruct IHHT as [t' H]. apply ST_Succ in H. eauto.
- (* T_Pred *)
destruct IHHT as [IHHT | IHHT].
+ apply (nat_canonical t1 HT) in IHHT. inversion IHHT; subst; right; eauto.
+ destruct IHHT as [t' H]. right. eauto.
- (* T_Iszero *)
destruct IHHT as [IHHT | IHHT].
+ apply (nat_canonical t1 HT) in IHHT. inversion IHHT; subst; right; eauto.
+ destruct IHHT as [t' H]. right. eauto.
Qed.
(** [] *)
(** **** Exercise: 3 stars, advanced (finish_progress_informal)
Complete the corresponding informal proof: *)
(** _Theorem_: If [|-- t \in T], then either [t] is a value or else
[t --> t'] for some [t']. *)
(** _Proof_: By induction on a derivation of [|-- t \in T].
- If the last rule in the derivation is [T_If], then [t = if t1
then t2 else t3], with [|-- t1 \in Bool], [|-- t2 \in T] and [|-- t3
\in T]. By the IH, either [t1] is a value or else [t1] can step
to some [t1'].
- If [t1] is a value, then by the canonical forms lemmas
and the fact that [|-- t1 \in Bool] we have that [t1]
is a [bvalue] -- i.e., it is either [true] or [false].
If [t1 = true], then [t] steps to [t2] by [ST_IfTrue],
while if [t1 = false], then [t] steps to [t3] by
[ST_IfFalse]. Either way, [t] can step, which is what
we wanted to show.
- If [t1] itself can take a step, then, by [ST_If], so can
[t].
- (* FILL IN HERE *)
*)
(* Do not modify the following line: *)
Definition manual_grade_for_finish_progress_informal : option (nat*string) := None.
(** [] *)
(** This theorem is more interesting than the strong progress theorem
that we saw in the [Smallstep] chapter, where _all_ normal forms
were values. Here a term can be stuck, but only if it is ill
typed. *)
(* ================================================================= *)
(** ** Type Preservation *)
(** The second critical property of typing is that, when a well-typed
term takes a step, the result is a well-typed term (of the same type). *)
(** **** Exercise: 2 stars, standard (finish_preservation) *)
Theorem preservation : forall t t' T,
<{ |-- t \in T }> ->
t --> t' ->
<{ |-- t' \in T }>.
(** Complete the formal proof of the [preservation] property. (Again,
make sure you understand the informal proof fragment in the
following exercise first.) *)
Proof.
intros t t' T HT HE.
generalize dependent t'.
induction HT;
(* every case needs to introduce a couple of things *)
intros t' HE;
(* and we can deal with several impossible
cases all at once *)
try solve_by_invert.
- (* T_If *) inversion HE; subst; clear HE.
+ (* ST_IFTrue *) assumption.
+ (* ST_IfFalse *) assumption.
+ (* ST_If *) apply T_If; try assumption.
apply IHHT1; assumption.
- (* T_Succ *) inversion HE; subst. apply IHHT in H0.
apply T_Succ. assumption.
- (* T_Pred *) inversion HE; subst; clear HE.
+ assumption.
+ inversion HT; subst. assumption.
+ apply IHHT in H0. apply T_Pred. assumption.
- (* T_Iszero *) inversion HE; subst; try constructor.
apply IHHT in H0. assumption.
Qed.
(** [] *)
(** **** Exercise: 3 stars, advanced (finish_preservation_informal)
Complete the following informal proof: *)
(** _Theorem_: If [|-- t \in T] and [t --> t'], then [|-- t' \in T]. *)
(** _Proof_: By induction on a derivation of [|-- t \in T].
- If the last rule in the derivation is [T_If], then [t = if t1
then t2 else t3], with [|-- t1 \in Bool], [|-- t2 \in T] and [|-- t3
\in T].
Inspecting the rules for the small-step reduction relation and
remembering that [t] has the form [if ...], we see that the
only ones that could have been used to prove [t --> t'] are
[ST_IfTrue], [ST_IfFalse], or [ST_If].
- If the last rule was [ST_IfTrue], then [t' = t2]. But we
know that [|-- t2 \in T], so we are done.
- If the last rule was [ST_IfFalse], then [t' = t3]. But we
know that [|-- t3 \in T], so we are done.
- If the last rule was [ST_If], then [t' = if t1' then t2
else t3], where [t1 --> t1']. We know [|-- t1 \in Bool] so,
by the IH, [|-- t1' \in Bool]. The [T_If] rule then gives us
[|-- if t1' then t2 else t3 \in T], as required.
- (* FILL IN HERE *)
*)
(* Do not modify the following line: *)
Definition manual_grade_for_finish_preservation_informal : option (nat*string) := None.
(** [] *)
(** **** Exercise: 3 stars, standard (preservation_alternate_proof)
Now prove the same property again by induction on the
_evaluation_ derivation instead of on the typing derivation.
Begin by carefully reading and thinking about the first few
lines of the above proofs to make sure you understand what
each one is doing. The set-up for this proof is similar, but
not exactly the same. *)
Theorem preservation' : forall t t' T,
<{ |-- t \in T }> ->
t --> t' ->
<{ |-- t' \in T }>.
Proof with eauto.
intros t t' T HT HE. generalize dependent T.
induction HE; intros T HT; try (inversion HT; subst; eauto).
- inversion H1; subst. assumption.
Qed.
(** [] *)
(** The preservation theorem is often called _subject reduction_,
because it tells us what happens when the "subject" of the typing
relation is reduced. This terminology comes from thinking of
typing statements as sentences, where the term is the subject and
the type is the predicate. *)
(* ================================================================= *)
(** ** Type Soundness *)
(** Putting progress and preservation together, we see that a
well-typed term can never reach a stuck state. *)
Definition multistep := (multi step).
Notation "t1 '-->*' t2" := (multistep t1 t2) (at level 40).
Corollary soundness : forall t t' T,
<{ |-- t \in T }> ->
t -->* t' ->
~(stuck t').
Proof.
intros t t' T HT P. induction P; intros [R S].
- apply progress in HT. destruct HT; auto.
- apply IHP.
+ apply preservation with (t := x); auto.
+ unfold stuck. split; auto.
Qed.
(* ================================================================= *)
(** ** Additional Exercises *)
(** **** Exercise: 3 stars, standard, especially useful (subject_expansion)
Having seen the subject reduction property, one might
wonder whether the opposite property -- subject _expansion_ --
also holds. That is, is it always the case that, if [t --> t']
and [|-- t' \in T], then [|-- t \in T]? If so, prove it. If
not, give a counter-example.
(* FILL IN HERE *)
It does not. Counter-example: <{ if true then true else 0 }>.
*)
Theorem subject_expansion:
(forall t t' T, t --> t' /\ <{ |-- t' \in T }> -> <{ |-- t \in T }>)
\/
~ (forall t t' T, t --> t' /\ <{ |-- t' \in T }> -> <{ |-- t \in T }>).
Proof.
right. intros contra.
specialize contra with <{ if true then true else 0 }> <{ true }> Bool.
assert (<{ if true then true else 0 }> --> <{ true }> /\ <{ |-- true \in Bool }>) by auto.
apply contra in H. inversion H; subst.
inversion H6.
Qed.
(** [] *)
(** **** Exercise: 2 stars, standard (variation1)
Suppose that we add this new rule to the typing relation:
| T_SuccBool : forall t,
<{ |-- t \in Bool }> ->
<{ |-- succ t \in Bool }>
Which of the following properties remain true in the presence of
this rule? For each one, write either "remains true" or
else "becomes false." If a property becomes false, give a
counterexample.
- Determinism of [step]
(* FILL IN HERE *)
Remains true
- Progress
(* FILL IN HERE *)
becomes false. Ex: <{ succ true }> is correctly typed but is stuck
- Preservation
(* FILL IN HERE *)
remains true
*)
(* Do not modify the following line: *)
Definition manual_grade_for_variation1 : option (nat*string) := None.
(** [] *)
(** **** Exercise: 2 stars, standard (variation2)
Suppose, instead, that we add this new rule to the [step] relation:
| ST_Funny1 : forall t2 t3,
(<{ if true then t2 else t3 }>) --> t3
Which of the above properties become false in the presence of
this rule? For each one that does, give a counter-example.
(* FILL IN HERE *)
Determinism of [step]:
becomes false <{ if true then 0 else 1 }> can either be 0 or 1
Progress
remains true
Preservation
remains true
*)
(* Do not modify the following line: *)
Definition manual_grade_for_variation2 : option (nat*string) := None.
(** [] *)
(** **** Exercise: 2 stars, standard, optional (variation3)
Suppose instead that we add this rule:
| ST_Funny2 : forall t1 t2 t2' t3,
t2 --> t2' ->
(<{ if t1 then t2 else t3 }>) --> (<{ if t1 then t2' else t3 }>)
Which of the above properties become false in the presence of
this rule? For each one that does, give a counter-example.
(* FILL IN HERE *)
Determinism of [step]:
becomes false <{ if false then 1=1 else false }> can either be <{ false }> or <{ if false then true else false }>
Progress:
remains true
Preservation:
remains true
*)
(** [] *)
(** **** Exercise: 2 stars, standard, optional (variation4)
Suppose instead that we add this rule:
| ST_Funny3 :
(<{pred false}>) --> (<{ pred (pred false)}>)
Which of the above properties become false in the presence of
this rule? For each one that does, give a counter-example.
(* FILL IN HERE *)
Determinism of [step]:
remains true
Progress:
remains true
Preservation:
remains true
*)
(** [] *)
(** **** Exercise: 2 stars, standard, optional (variation5)
Suppose instead that we add this rule:
| T_Funny4 :
|-- <{ 0 }> \in Bool
Which of the above properties become false in the presence of
this rule? For each one that does, give a counter-example.
(* FILL IN HERE *)
Determinism of [step]:
remains true
Progress:
becomes false <{ if 0 then 1 else 2 }>
Preservation:
becomes false <{|-- 1 \in Nat }> -> <{ |-- pred 1 \in Nat }>, <{ pred 1 }> --> <{ 0 }>, <{ |-- 0 \in Bool }>
*)
(** [] *)
(** **** Exercise: 2 stars, standard, optional (variation6)
Suppose instead that we add this rule:
| T_Funny5 :
|-- pred 0 }> \in Bool
Which of the above properties become false in the presence of
this rule? For each one that does, give a counter-example.
(* FILL IN HERE *)
Determinism of [step]:
remains true
Progress:
remains true
Preservation:
becomes false <{ |-- pred 0 \in Bool }>, <{ pred 0 }> --> <{ 0 }>, <{ |-- 0 \in Nat }>
*)
(** [] *)
(** **** Exercise: 3 stars, standard, optional (more_variations)
Make up some exercises of your own along the same lines as
the ones above. Try to find ways of selectively breaking
properties -- i.e., ways of changing the definitions that
break just one of the properties and leave the others alone.
*)
(* FILL IN HERE
[] *)
(** **** Exercise: 1 star, standard (remove_pred0)
The reduction rule [ST_Pred0] is a bit counter-intuitive: we
might feel that it makes more sense for the predecessor of [0] to
be undefined, rather than being defined to be [0]. Can we
achieve this simply by removing the rule from the definition of
[step]? Would doing so create any problems elsewhere?
(* FILL IN HERE *)
We can however it would make Progress become false as <{ pred 0 }> is in normal form but isn't a value
*)
(* Do not modify the following line: *)
Definition manual_grade_for_remove_pred0 : option (nat*string) := None.
(** [] *)
(** **** Exercise: 4 stars, advanced (prog_pres_bigstep)
Suppose our evaluation relation is defined in the big-step style.
State appropriate analogs of the progress and preservation
properties. (You do not need to prove them.)
Can you see any limitations of either of your properties? Do they
allow for nonterminating programs? Why might we prefer the
small-step semantics for stating preservation and progress?
(* FILL IN HERE *)
*)
Check progress.
(* Do not modify the following line: *)
Definition manual_grade_for_prog_pres_bigstep : option (nat*string) := None.
(** [] *)
End TM.
(* 2025-01-06 19:48 *)