lean2/tests/lean/tst17.lean.expected.out

  Set: pp::colors
  Set: pp::unicode
  Assumed: f
  Assumed: g
∀ a b : Type, ∃ c : Type, (g a b) = (f c)
∀ a b : Type, ∃ c : Type, (g a b) = (f c) : Bool
(λ a : Type,
   (λ b : Type, if ((λ x : Type, if ((g a b) == (f x)) ⊥ ⊤) == (λ x : Type, ⊤)) ⊥ ⊤) ==
   (λ x : Type, ⊤)) ==
(λ x : Type, ⊤)
-												Modify verbose message for Set command

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

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

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

											
										
										
											2013-09-03 17:44:51 +00: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-09-01 02:15:48 +00:00
+								  Assumed: f
 								  Assumed: g
-												Minimize use the colors in tests. The colors make the diff hard to read

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

											
										
										
											2013-09-01 17:34:57 +00:00
+								∀ a b : Type, ∃ c : Type, (g a b) = (f c)
-												Display the input term in the output of the Check command. It is useful to see the fully elaborated term.

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

											
										
										
											2013-09-09 05:54:22 +00:00
+								∀ a b : Type, ∃ c : Type, (g a b) = (f c) : Bool
-												Minimize use the colors in tests. The colors make the diff hard to read

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

											
										
										
											2013-09-01 17:34:57 +00:00
+								(λ a : Type,
-												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 23:20:02 +00:00
+								   (λ b : Type, if ((λ x : Type, if ((g a b) == (f x)) ⊥ ⊤) == (λ x : Type, ⊤)) ⊥ ⊤) ==
 								   (λ x : Type, ⊤)) ==
-												Minimize use the colors in tests. The colors make the diff hard to read

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

											
										
										
											2013-09-01 17:34:57 +00:00
+								(λ x : Type, ⊤)