Proof Repair across Type Equivalences — mentioned by tlringer

Thu, 25 Feb 2021 16:29:09 GMT

These problems are more closely related than you imagine. In particular, when you change a program, there is often necessarily more information you must give the computer in order to make the corresponding change in the proof. That additional burden is creativity, and is in many cases unavoidable. With good proof repair techniques you can fix the proof almost fully automatically in a way that mimics the change in the program, but then just ask the programmer a few questions to give the needed creativity to fix the proofs. As far as easy to understand goes, then, that "just" comes down to good…

Paper and discussion history. A mention is not an endorsement.

Proof Repair across Type Equivalences — mentioned by tlringer

Thu, 25 Feb 2021 16:22:24 GMT

This is my thesis area! If you're interested in proof repair, check out my latest work: https://arxiv.org/abs/2010.00774 More on my website: https://dependenttyp.es/ I hope more people work on this problem. It is a big and promising space. And I'll need students soon :)

Paper and discussion history. A mention is not an endorsement.

Proof Repair across Type Equivalences · HackerPapers discussions

Proof Repair across Type Equivalences — mentioned by tlringer

Proof Repair across Type Equivalences — mentioned by tlringer