Strongly typed term representations in Coq

Nick Benton, Chung-Kil Hur, Andrew Kennedy, Conor McBride

Research output: Contribution to journalArticle

34 Citations (Scopus)

Abstract

There are two approaches to formalizing the syntax of typed object languages in a proof assistant or programming language. The extrinsic approach is to first define a type that encodes untyped object expressions and then make a separate definition of typing judgements over the untyped terms. The intrinsic approach is to make a single definition that captures well-typed object expressions, so ill-typed expressions cannot even be expressed. Intrinsic encodings are attractive and naturally enforce the requirement that metalanguage operations on object expressions, such as substitution, respect object types. The price is that the metalanguage types of intrinsic encodings and operations involve non-trivial dependency, adding significant complexity. This paper describes intrinsic-style formalizations of both simply-typed and polymorphic languages, and basic syntactic operations thereon, in the Coq proof assistant. The Coq types encoding object-level variables (de Bruijn indices) and terms are indexed by both type and typing environment. One key construction is the boot-strapping of definitions and lemmas about the action of substitutions in terms of similar ones for a simpler notion of renamings. In the simply-typed case, this yields definitions that are free of any use of type equality coercions. In the polymorphic case, some substitution operations do still require type coercions, which we at least partially tame by uniform use of heterogeneous equality.
Original languageEnglish
Pages (from-to)141-159
Number of pages19
JournalJournal of Automated Reasoning
Volume49
Issue number2
DOIs
Publication statusPublished - Aug 2012

Keywords

  • Coq proof assistant
  • typed object languages
  • de Bruijn indices

Fingerprint Dive into the research topics of 'Strongly typed term representations in Coq'. Together they form a unique fingerprint.

Cite this