2016
DOI: 10.1007/978-3-319-43144-4_32
|View full text |Cite
|
Sign up to set email alerts
|

CoqPIE: An IDE Aimed at Improving Proof Development Productivity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…A few proof refactoring tools operate directly over tactics: POLAR [Dietrich et al 2013] refactors proof scripts in languages based on Isabelle/Isar [Wenzel 2007], CoqPIE [Roe and Smith 2016] is an IDE with support for simple refactorings of Ltac scripts, and Tactician [Adams 2015] is a proof script refactoring tool that focuses on switching between tactics and tacticals. This approach is not tractable for handling more complex changes; Robert [2018] discusses the challenges in detail.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…A few proof refactoring tools operate directly over tactics: POLAR [Dietrich et al 2013] refactors proof scripts in languages based on Isabelle/Isar [Wenzel 2007], CoqPIE [Roe and Smith 2016] is an IDE with support for simple refactorings of Ltac scripts, and Tactician [Adams 2015] is a proof script refactoring tool that focuses on switching between tactics and tacticals. This approach is not tractable for handling more complex changes; Robert [2018] discusses the challenges in detail.…”
Section: Related Workmentioning
confidence: 99%
“…There is no reason to believe that verifying a modified program is any easier than verifying the original the first time around. Tools that can automatically refactor or repair proofs [Adams 2015;Bourke et al 2012;Dietrich et al 2013;Ringer et al 2018;Robert 2018;Roe and Smith 2016;Whiteside 2013;Wibergh 2019] give us reason to believe that verifying a modified program can sometimes be easier than verifying the original the first time around, even when proof engineers do not follow good development processes, or when change occurs outside of proof engineers' control [Ringer et al 2019a]. Still, maintaining verified programs can be challenging: it means keeping not just the programs, but also the specifications and proofs about those programs up-to-date.…”
Section: Introductionmentioning
confidence: 99%
“…We briefly discussed two proactive approaches to this problem in Section 6.2.3: explicitly choosing identifiers to pass to intros, and writing tactics that do not refer to these hypotheses at all. In contrast with these proactive approaches, the IDE CoqPIE (Roe and Smith, 2016) automatically renames references to hypotheses in proofs to work around this problem reactively.…”
Section: Proof Evolutionmentioning
confidence: 99%
“…Many of the user support features that are now arising for proof engineering echo similar features that already exist in languages with more mature IDEs. For example, languages with more mature IDEs often integrate refactoring tools into those IDEs; now that proof assistant interfaces are maturing, interfaces with refactoring support such the Coq interface CoqPIE (Roe and Smith, 2016) are beginning to emerge. We discuss more refactoring tools in Section 7.2.2.…”
Section: Tooling For User Supportmentioning
confidence: 99%
See 1 more Smart Citation