Hostname: page-component-74656f9884-c52kr Total loading time: 0 Render date: 2026-11-09T03:21:32.710Z Has data issue: false hasContentIssue false

Foundations of dependent interoperability

Published online by Cambridge University Press:  13 March 2018

PIERRE-ÉVARISTE DAGAND
Affiliation:
Sorbonne Universités, UPMC Univ Paris 06, CNRS, INRIA, LIP6 UMR 7606, Paris, France (e-mail: pierre-evariste.dagand@inria.fr)
NICOLAS TABAREAU
Affiliation:
INRIA, Paris, France (e-mail: nicolas.tabareau@inria.fr)
ÉRIC TANTER
Affiliation:
PLEIAD Lab, Computer Science Dept (DCC), University of Chile, Santiago, Chile (e-mail: etanter@dcc.uchile.cl)
Rights & Permissions [Opens in a new window]

Abstract

Core share and HTML view are not available for this content. However, as you have access to this content, a full PDF is available via the 'Save PDF' action button.

Full-spectrum dependent types promise to enable the development of correct-by-construction software. However, even certified software needs to interact with simply-typed or untyped programs, be it to perform system calls, or to use legacy libraries. Trading static guarantees for runtime checks, the dependent interoperability framework provides a mechanism by which simply-typed values can safely be coerced to dependent types and, conversely, dependently-typed programs can defensively be exported to a simply-typed application. In this article, we give a semantic account of dependent interoperability. Our presentation relies on and is guided by a pervading notion of type equivalence, whose importance has been emphasized in recent work on homotopy type theory. Specifically, we develop the notions of type-theoretic partial Galois connections as a key foundation for dependent interoperability, which accounts for the partiality of the coercions between types. We explore the applicability of both type-theoretic Galois connections and anticonnections in the setting of dependent interoperability. A partial Galois connection enforces a translation of dependent types to runtime checks that are both sound and complete with respect to the invariants encoded by dependent types. Conversely, picking an anticonnection instead lets us induce weaker, sound conditions that can amount to more efficient runtime checks.

Our framework is developed in Coq; it is thus constructive and verified in the strictest sense of the terms. Using our library, users can specify domain-specific partial connections between data structures. Our library then takes care of the (sometimes, heavy) lifting that leads to interoperable programs. It thus becomes possible, as we shall illustrate, to internalize and hand-tune the extraction of dependently-typed programs to interoperable OCaml programs within Coq itself.

Information

Type
Articles
Copyright
Copyright © Cambridge University Press 2018 
Submit a response

Discussions

No Discussions have been published for this article.