lean2/tests/lean/tst5.lean.expected.out

  Set: pp::colors
  Set: pp::unicode
  Assumed: N
  Assumed: a
  Assumed: b
a = b
a = b : Bool
  Set: lean::pp::implicit
eq::explicit N a b
eq::explicit (Type 2) (Type 1) (Type 1)
eq::explicit Bool ⊤ ⊥
-												Modify verbose message for Set command

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-09-02 12:29:21 -07:00
+								  Set: pp::colors
-												Fix unit tests for Windows

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-09-03 10:44:51 -07:00
+								  Set: pp::unicode
-												Move files in examples directory to tests directory. They are not real examples

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-08-31 19:15:48 -07:00
+								  Assumed: N
 								  Assumed: a
 								  Assumed: b
-												refactor(equality): make homogeneous equality the default equality

It was not a good idea to use heterogeneous equality as the default equality in Lean.
It creates the following problems.

- Heterogeneous equality does not propagate constraints in the elaborator.
For example, suppose that l has type (List Int), then the expression
     l = nil
will not propagate the type (List Int) to nil.

- It is easy to write false. For example, suppose x has type Real, and the user
writes x = 0. This is equivalent to false, since 0 has type Nat. The elaborator cannot introduce
the coercion since x = 0 is a type correct expression.

Homogeneous equality does not suffer from the problems above.
We keep heterogeneous equality because it is useful for generating proof terms.

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-10-29 16:20:02 -07:00
+								a = b
 								a = b : Bool
-												Modify verbose message for Set command

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-09-02 12:29:21 -07:00
+								  Set: lean::pp::implicit
-												refactor(equality): make homogeneous equality the default equality

It was not a good idea to use heterogeneous equality as the default equality in Lean.
It creates the following problems.

- Heterogeneous equality does not propagate constraints in the elaborator.
For example, suppose that l has type (List Int), then the expression
     l = nil
will not propagate the type (List Int) to nil.

- It is easy to write false. For example, suppose x has type Real, and the user
writes x = 0. This is equivalent to false, since 0 has type Nat. The elaborator cannot introduce
the coercion since x = 0 is a type correct expression.

Homogeneous equality does not suffer from the problems above.
We keep heterogeneous equality because it is useful for generating proof terms.

Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>

											
										
										
											2013-10-29 16:20:02 -07:00
+								eq::explicit N a b
 								eq::explicit (Type 2) (Type 1) (Type 1)
 								eq::explicit Bool ⊤ ⊥