-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get arguments for tactic of form simple_intropattern_list(x)
#505
Comments
I see two ways forward. From elpi Require Import elpi.
Elpi Tactic app.
Elpi Accumulate lp:{{
solve (goal _ _ _ _ [str X] as G) GL :- coq.ltac.call-ltac1 X G GL.
}}.
Elpi Typecheck.
Goal forall n, n + 1 = 1.
let tac := intros n in
elpi app "tac". here The better option would be to expose to elpi this data type This latter option would make it possible to craft this data in elpi, and not just pass it along. |
Sorry, the implicit question is: would the first approach suffice for your use case? |
Yes, I think this would work. I only need to call intros on an intro pattern that I have been given by the user on the tactic for now. Tactic Notation "eiIntros" "(" simple_intropattern_list(x) ")" :=
let coqintro := intros x in
elpi eiIntros coqintro "". |
After having a talk with my supervisor, I'm sorry to say, it turns out we actually do need to have full access to the intro pattern data type. We have to pull it apart and apply our own steps in between applications of parts of the intro pattern. Also we would need to create new ones from scratch. Would this be possible? |
I need to write an Intro tactic that also allows for receiving normal intro patterns and also my own intro patterns. To be able to properly accept an intro pattern, I need to have a notation in the form of:
amongst other notations.
It would thus be nice to be able to read in an intro pattern list, be able to manipulate it when necessary and pass it on to the intro tactic.
The text was updated successfully, but these errors were encountered: