Datatype Rules: Difference between revisions
imported>Nicolas |
imported>Nicolas |
||
Line 61: | Line 61: | ||
=== Application to lists === | === Application to lists === | ||
Starting from goal | |||
<math>\forall l \qdot \exists x \qdot \operatorname{member}(x,l) \land (\forall y \qdot \operatorname{member}(y,l) \limp y \leq x)</math> | |||
we can free variable l then apply Distinct Case on it: | |||
This shows that nil list has been forgotten in the predicate. | |||
=== Application to trees === | === Application to trees === |
Revision as of 16:53, 6 September 2010
Datatype rules may seem a bit difficult to understand at first sight. Here are a few examples intended to make them clearer.
Datatypes used
The rules will be applied to the following datatypes:
Directions:
direction ::= north | east | south | west
Let us have a function
first two arguments are a start position, third is a direction, result is the end position.
Lists:
list(T) ::= nil | cons( head : T, tail : list(T) )
Let us have a predicate
meaning that the first argument is a member of the list.
Trees:
tree(T) ::= empty | node( left : tree(T), value : T, right : tree(T) )
Let us have a function
defining the height of a tree
Distinct Case
The rule states
Application to directions
Starting from goal
we can free variables x,y,d then apply Distinct Case:
The resulting proof step is
further simplifications depend on the existence of rules about move and the various directions.
Application to lists
Starting from goal
we can free variable l then apply Distinct Case on it:
This shows that nil list has been forgotten in the predicate.
Application to trees
TODO
!l,v,r. t = node(l,v,r) => height(l) < height(t)
Induction
TODO