Closed Zdancewic closed 5 years ago
It makes sense to rename. Let's do it.
Ok -- I'll rename it to 'go' for now. I don't think that introduces any clashes.
OK -- there were two different uses of do
.
do
to go
in itreedo
to lift
for the OpenSum stuff. (Maybe lift
should be something better?)
Currently the record that we use for the itree CoInductive uses
do
as the constructor name, but I was running into some issues writing tactics that look fordo
because it is also an Ltac keyword. Should we changedo
togo
or something else?(It could also be that the tactics I'm trying to write should be written in a different way, which wouldn't run into the conflict.)