2014
DOI: 10.1007/978-3-319-08970-6_24
|View full text |Cite
|
Sign up to set email alerts
|

Compositional Computational Reflection

Abstract: Abstract. Current work on computational reflection is single-minded; each reflective procedure is written with a specific application or scope in mind. Composition of these reflective procedures is done by a proofgenerating tactic language such as Ltac. This composition, however, comes at the cost of both larger proof terms and redundant preprocessing. In this work, we propose a methodology for writing composable reflective procedures that solve many small tasks in a single invocation. The key technical insigh… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2014
2014
2017
2017

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 15 publications
(7 citation statements)
references
References 21 publications
0
7
0
Order By: Relevance
“…Proofs by reflection has been intensively studied [5,16], but without anything similar to the type-safe reflection that we have presented here. If we leave the ground of nice mathematical structures, one can decide to work with arbitrary rewriting rules, but in the general case there isn't a complete decision procedure for such systems, because there is usually no normal form.…”
Section: Related Workmentioning
confidence: 99%
“…Proofs by reflection has been intensively studied [5,16], but without anything similar to the type-safe reflection that we have presented here. If we leave the ground of nice mathematical structures, one can decide to work with arbitrary rewriting rules, but in the general case there isn't a complete decision procedure for such systems, because there is usually no normal form.…”
Section: Related Workmentioning
confidence: 99%
“…Recent work by Malecha et al (2014) restricts the use of reflection to reflective hints. Hints are lemmas reflected into an inductive datatype, similar to what the reflection mechanism of Agda does, packed together with a proof of soundness.…”
Section: Typechecked Tactics Through Reflectionmentioning
confidence: 99%
“…Figure 9 shows an excerpt from a real Coq source file, ending in the full code to prove that invariants are never violated. The proof is almost entirely automated, appealing to the separationlogic proof procedures that Bedrock provides [25]. This level of automation persists in verifications of more featureful client code, and it represents a qualitative improvement to the ease of building on verified systems libraries, compared to past work.…”
Section: A Thread-library Component Stackmentioning
confidence: 99%