lean2/tests/lean/tst9.lean.expected.out

  Set: pp::colors
  Set: pp::unicode
  Assumed: f
  Assumed: N
  Assumed: g
  Assumed: a
tst9.lean:5:6: error: type mismatch in argument #1 at application
    g ⊤ (f ?M::0 a a)
Function type:
    N → N → Bool
Arguments types:
    ⊤ : Bool
    f ?M::0 a a : ?M::0
-												Improve application type mismatch error messages

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

											
										
										
											2013-09-02 18:28:12 -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: f
 								  Assumed: N
 								  Assumed: g
 								  Assumed: a
-												feat(kernel/type_checker): improve application type mismatch error messages

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

											
										
										
											2014-01-27 09:45:17 -08:00
+								tst9.lean:5:6: error: type mismatch in argument #1 at application
-												refactor(kernel/metavar): avoid using unique names for default metavariable prefix

The problem is that unique names depend on the order compilation units are initialized. The order of initialization is not specified by the C++ standard. Then, different compilers (or even the same compiler) may produce different initialization orders, and consequently the metavariable prefix is going to be different for different builds. This is not a bug, but it makes unit tests to fail since the output produced by different builds is different for the same input file.
Avoiding unique name feature in the default metavariable prefix avoids this problem.

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

											
										
										
											2013-11-07 10:16:22 -08:00
+								    g ⊤ (f ?M::0 a a)
-												Improve error messages when overloads+coercions do not work

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

											
										
										
											2013-09-02 20:05:47 -07:00
+								Function type:
-												Improve application type mismatch error messages

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

											
										
										
											2013-09-02 18:28:12 -07:00
+								    N → N → Bool
-												Improve error messages when overloads+coercions do not work

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

											
										
										
											2013-09-02 20:05:47 -07:00
+								Arguments types:
-												Improve application type mismatch errors. We also show the implicit arguments (not just their types)

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

											
										
										
											2013-09-04 10:23:51 -07:00
+								    ⊤ : Bool
-												refactor(kernel/metavar): avoid using unique names for default metavariable prefix

The problem is that unique names depend on the order compilation units are initialized. The order of initialization is not specified by the C++ standard. Then, different compilers (or even the same compiler) may produce different initialization orders, and consequently the metavariable prefix is going to be different for different builds. This is not a bug, but it makes unit tests to fail since the output produced by different builds is different for the same input file.
Avoiding unique name feature in the default metavariable prefix avoids this problem.

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

											
										
										
											2013-11-07 10:16:22 -08:00
+								    f ?M::0 a a : ?M::0