9c60eed93c
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>
44 lines
1.2 KiB
Text
44 lines
1.2 KiB
Text
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
|