mathlib4
mathlib4 copied to clipboard
feat: `rename_bvar` tactic
Also, I don't understand that lint error from the CI tests
What's the reasoning behind changing the tactic from rename_var to rename_bvar?
rename_var is not explicit enough and when looking at its name alone I was mistaken about its behavior. The fact is that this tactic only renames bound variables.
I have a fix for this, but I don't have the necessary rights to push to this branch yet. @digama0 could I get these?
I replaced your API for modifyLocalContext etc. with an API that is arguably more in line with the core APIs, though whether that makes it better is another question. Feel free to revert if you don't like it.
@JLimperg
I replaced your API for
modifyLocalContextetc. with an API that is arguably more in line with the core APIs, though whether that makes it better is another question. Feel free to revert if you don't like it.
I think there are benefits from having a function that already lives in MetaM to give more power to the user, no?
Yes. The advantage of my API is that it works for any MonadMCtx and does not need to create additional metavariables. But there's certainly a tradeoff here. If you put my API in MetaM, you could get around the restriction that modifyMCtx only accepts a pure function; that might give you the best of both worlds.
There are merge conflicts now.
bors d+
bors r+