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
    Substitution
     ⊢ Bool ≺ ?M::0
        (line: 5: pos: 6) Type of argument 2 must be convertible to the expected type in the application of
            myeq
        with arguments:
            ?M::0
            ⊤
            a
        Assignment
         ⊢ T ≺ ?M::0
            (line: 5: pos: 6) Type of argument 3 must be convertible to the expected type in the application of
                myeq
            with arguments:
                ?M::0
                ⊤
                a
  Assumed: myeq2
  Set: lean::pp::implicit
Failed to solve
 ⊢ Bool ≺ T
    Substitution
     ⊢ Bool ≺ ?M::0
        (line: 9: pos: 15) Type of argument 2 must be convertible to the expected type in the application of
            myeq2::explicit
        with arguments:
            ?M::0
            ⊤
            a
        Assignment
         ⊢ T ≺ ?M::0
            (line: 9: pos: 15) Type of argument 3 must be convertible to the expected type in the application of
                myeq2::explicit
            with arguments:
                ?M::0
                ⊤
                a
-												Improve application type mismatch error messages

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

											
										
										
											2013-09-03 01:28:12 +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
-												Add more tests

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

											
										
										
											2013-09-01 01:46:18 +00: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-25 02:08:35 +00:00
+								Failed to solve
 								 ⊢ Bool ≺ T
 								    Substitution
-												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 18:16:22 +00:00
+								     ⊢ Bool ≺ ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								        (line: 5: pos: 6) Type of argument 2 must be convertible to the expected type in the application of
 								            myeq
 								        with arguments:
-												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 18:16:22 +00:00
+								            ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								            ⊤
 								            a
 								        Assignment
-												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 18:16:22 +00:00
+								         ⊢ T ≺ ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								            (line: 5: pos: 6) Type of argument 3 must be convertible to the expected type in the application of
 								                myeq
 								            with arguments:
-												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 18:16:22 +00:00
+								                ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								                ⊤
 								                a
-												Add more tests

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

											
										
										
											2013-09-01 01:46:18 +00:00
+								  Assumed: myeq2
-												Modify verbose message for Set command

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

											
										
										
											2013-09-02 19:29:21 +00: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-25 02:08:35 +00:00
+								Failed to solve
 								 ⊢ Bool ≺ T
 								    Substitution
-												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 18:16:22 +00:00
+								     ⊢ Bool ≺ ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								        (line: 9: pos: 15) Type of argument 2 must be convertible to the expected type in the application of
 								            myeq2::explicit
 								        with arguments:
-												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 18:16:22 +00:00
+								            ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								            ⊤
 								            a
 								        Assignment
-												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 18:16:22 +00:00
+								         ⊢ T ≺ ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								            (line: 9: pos: 15) Type of argument 3 must be convertible to the expected type in the application of
 								                myeq2::explicit
 								            with arguments:
-												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 18:16:22 +00:00
+								                ?M::0
-												fix(tests/lean): adjust error messages in the expected output

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

											
										
										
											2013-10-25 02:08:35 +00:00
+								                ⊤
 								                a