lean2/tests/lean/bug.lean.expected.out

  Set: pp::colors
  Set: pp::unicode
Failed to solve
A : (Type U), A' : (Type U), H : A == A' ⊢ ?M::3 ≺ TypeU
    bug.lean:1:44: Type of argument 1 must be convertible to the expected type in the application of
        @symm
    with arguments:
        ?M::0
        A
        A'
        H
test(tests/lean): add example that cannot be elaborated Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-12-21 12:19:53 +00:00			`Set: pp::colors`
			`Set: pp::unicode`
			`Failed to solve`
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-04 01:13:10 +00:00			`A : (Type U), A' : (Type U), H : A == A' ⊢ ?M::3 ≺ TypeU`
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 20:15:12 +00:00			`bug.lean:1:44: Type of argument 1 must be convertible to the expected type in the application of`
feat(*): change name conventions for Lean builtin libraries Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2014-01-06 03:10:21 +00:00			`@symm`
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-04 01:13:10 +00:00			`with arguments:`
			`?M::0`
			`A`
			`A'`
			`H`