lean2/tests/lean/ex3.lean.expected.out

  Set: pp::colors
  Set: pp::unicode
  Assumed: myeq
myeq Bool ⊤ ⊥
  Assumed: T
  Assumed: a
Failed to solve
 ⊢ Bool ≺ T
    ex3.lean:5:6: Type of argument 2 must be convertible to the expected type in the application of
        myeq
    with arguments:
        T
        ⊤
        a
  Assumed: myeq2
  Set: lean::pp::implicit
Failed to solve
 ⊢ Bool ≺ T
    ex3.lean:9:11: Type of argument 2 must be convertible to the expected type in the application of
        @myeq2
    with arguments:
        T
        ⊤
        a
-												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
-												Add more tests

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

											
										
										
											2013-08-31 18:46:18 -07:00
+								  Assumed: myeq
 								myeq Bool ⊤ ⊥
 								  Assumed: T
 								  Assumed: a
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-24 19:08:35 -07:00
+								Failed to solve
 								 ⊢ Bool ≺ T
-												feat(kernel/pos_info_provider): add support for file names in pos_info_provider

The idea is to include the file name when displaying justification objects.

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

											
										
										
											2014-01-09 12:15:12 -08:00
+								    ex3.lean:5:6: Type of argument 2 must be convertible to the expected type in the application of
-												feat(kernel, library/elaborator, frontends/lean): improve how elaborator_exceptions are displayed in the Lean frontend

This commit affects different modules.
I used the following approach:
1- I store the metavariable environment at unification_failure_justifications. The idea is to capture the set of instantiated metavariables at the time of failure.
2- I added a remove_detail function. It removes propagation steps from the justification tree object. I also remove the backtracking search space associated with higher-order unificiation. I keep only the search related to case-splits due to coercions and overloads.

3- I use the metavariable environment captured at step 1 when pretty printing the justification of an elaborator_exception.

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

											
										
										
											2014-01-03 17:13:10 -08:00
+								        myeq
 								    with arguments:
 								        T
 								        ⊤
 								        a
-												Add more tests

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

											
										
										
											2013-08-31 18:46:18 -07:00
+								  Assumed: myeq2
-												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
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-24 19:08:35 -07:00
+								Failed to solve
 								 ⊢ Bool ≺ T
-												feat(kernel/pos_info_provider): add support for file names in pos_info_provider

The idea is to include the file name when displaying justification objects.

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

											
										
										
											2014-01-09 12:15:12 -08:00
+								    ex3.lean:9:11: Type of argument 2 must be convertible to the expected type in the application of
-												feat(kernel, library/elaborator, frontends/lean): improve how elaborator_exceptions are displayed in the Lean frontend

This commit affects different modules.
I used the following approach:
1- I store the metavariable environment at unification_failure_justifications. The idea is to capture the set of instantiated metavariables at the time of failure.
2- I added a remove_detail function. It removes propagation steps from the justification tree object. I also remove the backtracking search space associated with higher-order unificiation. I keep only the search related to case-splits due to coercions and overloads.

3- I use the metavariable environment captured at step 1 when pretty printing the justification of an elaborator_exception.

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

											
										
										
											2014-01-03 17:13:10 -08:00
+								        @myeq2
 								    with arguments:
 								        T
 								        ⊤
 								        a