lean4-htt/tests/lean/crash.lean.expected.out
Leonardo de Moura cce88c6190 refactor(frontends/lean): interactive tactic support
After this commit, new interactice tactic classes can be added without
writing C++ code (see example: tests/lean/run/my_tac_class.lean).

The tactic_evaluator was simplified, and all the complexity has been
moved to tactic_notation, and lean code.

We can now inspect the intermediate states produced by the rewrite
tactic.

The function (@scope_trace _ line col thunk) can be used to position trace
messages produced by thunk. If line/col are not provided (i.e., we
just write (scope_trace thunk)), then line/col are filled with the
position of this term by the elaborator.

We can visualize the intermediate tactic states inside nested blocks
such as (try { ... })

The new infrastructure can be used to implement custom tactic_state
pretty printers.
2017-01-21 22:38:47 -08:00

10 lines
206 B
Text

crash.lean:6:11: error: don't know how to synthesize placeholder
context:
P : Prop
⊢ Type ?
crash.lean:9:17: error: invalid have-expression, expression
H
has type
P
but is expected to have type
¬P