You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When strategies such as kt generate multiple subgoals to prove a claim,
we currently use the | operator to handle each branch.
This is a bit mucky, since the strategies intended for the initial goals
are also discharged against the later goals complicating debugging.
e.g. If we have:
claim a /\ b
strategy and-split . ( strat-for-a | strat-for-b )
strat-for-a is used to prove a. Then, the prover first tries strat-for-a
to prove b, and fails. It then tries the second branch of the choice.
We propose two new strategies: one for introducing branches in to a proof-tree
and another for resolving them.
When the &> is followed by a strategy that is not <| it behaves
identically to &.
However, when followed by the <| strategy, each sub-strategy in the &>
is paired with the corresponding strategy in <|.
The text was updated successfully, but these errors were encountered:
When strategies such as
kt
generate multiple subgoals to prove a claim,we currently use the
|
operator to handle each branch.This is a bit mucky, since the strategies intended for the initial goals
are also discharged against the later goals complicating debugging.
e.g. If we have:
strat-for-a
is used to provea
. Then, the prover first triesstrat-for-a
to prove
b
, and fails. It then tries the second branch of the choice.We propose two new strategies: one for introducing branches in to a proof-tree
and another for resolving them.
When the
&>
is followed by a strategy that is not<|
it behavesidentically to
&
.However, when followed by the
<|
strategy, each sub-strategy in the&>
is paired with the corresponding strategy in
<|
.The text was updated successfully, but these errors were encountered: