Generalize (e)feed pose proof to intro patterns
This appears a simple oversight, since pose proof
takes an intro pattern
anyway; feed inversion
and feed destruct
already take intro patterns, and
I've been using the generalized efeed pose proof
for a while.
Merge request reports
Activity
More intro patterns is better.
However, I'd like to understand the rationale: what is the advantage compared to using
destruct
andedestruct
here? They already create goals for all arguments.Edited by Robbert Krebbersping @Blaisorblade
Please register or sign in to reply