An Anti-Locally-Nameless Approach to Formalizing Quantifiers Olivier Laurent
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Experience Implementing a Performant Category-Theory Library in Coq
Experience Implementing a Performant Category-Theory Library in Coq Jason Gross, Adam Chlipala, and David I. Spivak Massachusetts Institute of Technology, Cambridge, MA, USA [email protected], [email protected], [email protected] Abstract. We describe our experience implementing a broad category- theory library in Coq. Category theory and computational performance are not usually mentioned in the same breath, but we have needed sub- stantial engineering effort to teach Coq to cope with large categorical constructions without slowing proof script processing unacceptably. In this paper, we share the lessons we have learned about how to repre- sent very abstract mathematical objects and arguments in Coq and how future proof assistants might be designed to better support such rea- soning. One particular encoding trick to which we draw attention al- lows category-theoretic arguments involving duality to be internalized in Coq's logic with definitional equality. Ours may be the largest Coq development to date that uses the relatively new Coq version developed by homotopy type theorists, and we reflect on which new features were especially helpful. Keywords: Coq · category theory · homotopy type theory · duality · performance 1 Introduction Category theory [36] is a popular all-encompassing mathematical formalism that casts familiar mathematical ideas from many domains in terms of a few unifying concepts. A category can be described as a directed graph plus algebraic laws stating equivalences between paths through the graph. Because of this spar- tan philosophical grounding, category theory is sometimes referred to in good humor as \formal abstract nonsense." Certainly the popular perception of cat- egory theory is quite far from pragmatic issues of implementation. -
MOTIVATING HILBERT SYSTEMS Hilbert Systems Are Formal Systems
MOTIVATING HILBERT SYSTEMS Hilbert systems are formal systems that encode the notion of a mathematical proof, which are used in the branch of mathematics known as proof theory. There are other formal systems that proof theorists use, with their own advantages and disadvantages. The advantage of Hilbert systems is that they are simpler than the alternatives in terms of the number of primitive notions they involve. Formal systems for proof theory work by deriving theorems from axioms using rules of inference. The distinctive characteristic of Hilbert systems is that they have very few primitive rules of inference|in fact a Hilbert system with just one primitive rule of inference, modus ponens, suffices to formalize proofs using first- order logic, and first-order logic is sufficient for all mathematical reasoning. Modus ponens is the rule of inference that says that if we have theorems of the forms p ! q and p, where p and q are formulas, then χ is also a theorem. This makes sense given the interpretation of p ! q as meaning \if p is true, then so is q". The simplicity of inference in Hilbert systems is compensated for by a somewhat more complicated set of axioms. For minimal propositional logic, the two axiom schemes below suffice: (1) For every pair of formulas p and q, the formula p ! (q ! p) is an axiom. (2) For every triple of formulas p, q and r, the formula (p ! (q ! r)) ! ((p ! q) ! (p ! r)) is an axiom. One thing that had always bothered me when reading about Hilbert systems was that I couldn't see how people could come up with these axioms other than by a stroke of luck or genius. -
Testing Noninterference, Quickly
Testing Noninterference, Quickly Cat˘ alin˘ Hrit¸cu1 John Hughes2 Benjamin C. Pierce1 Antal Spector-Zabusky1 Dimitrios Vytiniotis3 Arthur Azevedo de Amorim1 Leonidas Lampropoulos1 1University of Pennsylvania 2Chalmers University 3Microsoft Research Abstract To answer this question, we take as a case study the task of Information-flow control mechanisms are difficult to design and extending a simple abstract stack-and-pointer machine to track dy- labor intensive to prove correct. To reduce the time wasted on namic information flow and enforce termination-insensitive nonin- proof attempts doomed to fail due to broken definitions, we ad- terference [23]. Although our machine is simple, this exercise is vocate modern random testing techniques for finding counterexam- both nontrivial and novel. While simpler notions of dynamic taint ples during the design process. We show how to use QuickCheck, tracking are well studied for both high- and low-level languages, a property-based random-testing tool, to guide the design of a sim- it has only recently been shown [1, 24] that dynamic checks are ple information-flow abstract machine. We find that both sophis- capable of soundly enforcing strong security properties. Moreover, ticated strategies for generating well-distributed random programs sound dynamic IFC has been studied only in the context of lambda- and readily falsifiable formulations of noninterference properties calculi [1, 16, 25] and While programs [24]; the unstructured con- are critically important. We propose several approaches and eval- trol flow of a low-level machine poses additional challenges. (Test- uate their effectiveness on a collection of injected bugs of varying ing of static IFC mechanisms is left as future work.) subtlety. -
Mathematics in the Computer
Mathematics in the Computer Mario Carneiro Carnegie Mellon University April 26, 2021 1 / 31 Who am I? I PhD student in Logic at CMU I Proof engineering since 2013 I Metamath (maintainer) I Lean 3 (maintainer) I Dabbled in Isabelle, HOL Light, Coq, Mizar I Metamath Zero (author) Github: digama0 I Proved 37 of Freek’s 100 theorems list in Zulip: Mario Carneiro Metamath I Lots of library code in set.mm and mathlib I Say hi at https://leanprover.zulipchat.com 2 / 31 I Found Metamath via a random internet search I they already formalized half of the book! I .! . and there is some stuff on cofinality they don’t have yet, maybe I can help I Got involved, did it as a hobby for a few years I Got a job as an android developer, kept on the hobby I Norm Megill suggested that I submit to a (Mizar) conference, it went well I Met Leo de Moura (Lean author) at a conference, he got me in touch with Jeremy Avigad (my current advisor) I Now I’m a PhD at CMU philosophy! How I got involved in formalization I Undergraduate at Ohio State University I Math, CS, Physics I Reading Takeuti & Zaring, Axiomatic Set Theory 3 / 31 I they already formalized half of the book! I .! . and there is some stuff on cofinality they don’t have yet, maybe I can help I Got involved, did it as a hobby for a few years I Got a job as an android developer, kept on the hobby I Norm Megill suggested that I submit to a (Mizar) conference, it went well I Met Leo de Moura (Lean author) at a conference, he got me in touch with Jeremy Avigad (my current advisor) I Now I’m a PhD at CMU philosophy! How I got involved in formalization I Undergraduate at Ohio State University I Math, CS, Physics I Reading Takeuti & Zaring, Axiomatic Set Theory I Found Metamath via a random internet search 3 / 31 I . -
Applications of Non-Classical Logic Andrew Tedder University of Connecticut - Storrs, [email protected]
University of Connecticut OpenCommons@UConn Doctoral Dissertations University of Connecticut Graduate School 8-8-2018 Applications of Non-Classical Logic Andrew Tedder University of Connecticut - Storrs, [email protected] Follow this and additional works at: https://opencommons.uconn.edu/dissertations Recommended Citation Tedder, Andrew, "Applications of Non-Classical Logic" (2018). Doctoral Dissertations. 1930. https://opencommons.uconn.edu/dissertations/1930 Applications of Non-Classical Logic Andrew Tedder University of Connecticut, 2018 ABSTRACT This dissertation is composed of three projects applying non-classical logic to problems in history of philosophy and philosophy of logic. The main component concerns Descartes’ Creation Doctrine (CD) – the doctrine that while truths concerning the essences of objects (eternal truths) are necessary, God had vol- untary control over their creation, and thus could have made them false. First, I show a flaw in a standard argument for two interpretations of CD. This argument, stated in terms of non-normal modal logics, involves a set of premises which lead to a conclusion which Descartes explicitly rejects. Following this, I develop a multimodal account of CD, ac- cording to which Descartes is committed to two kinds of modality, and that the apparent contradiction resulting from CD is the result of an ambiguity. Finally, I begin to develop two modal logics capturing the key ideas in the multi-modal interpretation, and provide some metatheoretic results concerning these logics which shore up some of my interpretive claims. The second component is a project concerning the Channel Theoretic interpretation of the ternary relation semantics of relevant and substructural logics. Following Barwise, I de- velop a representation of Channel Composition, and prove that extending the implication- conjunction fragment of B by composite channels is conservative. -
Xmonad in Coq: Programming a Window Manager in a Proof Assistant
xmonad in Coq Programming a window manager in a proof assistant Wouter Swierstra Haskell Symposium 2012 Coq Coq • Coq is ‘just’ a total functional language; • Extraction lets you turn Coq programs into OCaml, Haskell, or Scheme code. • Extraction discards proofs, but may introduce ‘unsafe’ coercions. Demo Extraction to Haskell is not popular. xmonad xmonad • A tiling window manager for X: • arranges windows over the whole screen; • written and configured in Haskell; • has several tens of thousands of users. xmonad: design principles ReaderT StateT IO monad This paper • This paper describes a reimplementation of xmonad’s pure core in Coq; • Extracting Haskell code produces a drop-in replacement for the original module; • Documents my experience. Does it work? Blood Sweat Shell script What happens in the functional core? Data types data Zipper a = Zipper { left :: [a] , focus :: !a , right :: [a] } ... and a lot of functions for zipper manipulation Totality • This project is feasible because most of the functions are structurally recursive. • What about this function? focusLeft (Zipper [] x rs) = let (y : ys) = reverse (x : rs) in Zipper ys y [] Extraction • The basic extracted code is terrible! • uses Peano numbers, extracted Coq booleans, etc. • uses extracted Coq data types for zippers; • generates ‘non-idiomatic’ Haskell. Customizing extraction • There are various hooks to customize the extracted code: • inlining functions; • realizing axioms; • using Haskell data types. Interfacing with Haskell • We would like to use ‘real’ Haskell booleans Extract Inductive bool => "Bool" ["True" "False" ]. • Lots of opportunity to shoot yourself in the foot! Better extracted code • The extracted file uses generated data types and exports ‘too much’ • Solution: • Customize extraction to use hand-coded data types. -
A Survey of Engineering of Formally Verified Software
The version of record is available at: http://dx.doi.org/10.1561/2500000045 QED at Large: A Survey of Engineering of Formally Verified Software Talia Ringer Karl Palmskog University of Washington University of Texas at Austin [email protected] [email protected] Ilya Sergey Milos Gligoric Yale-NUS College University of Texas at Austin and [email protected] National University of Singapore [email protected] Zachary Tatlock University of Washington [email protected] arXiv:2003.06458v1 [cs.LO] 13 Mar 2020 Errata for the present version of this paper may be found online at https://proofengineering.org/qed_errata.html The version of record is available at: http://dx.doi.org/10.1561/2500000045 Contents 1 Introduction 103 1.1 Challenges at Scale . 104 1.2 Scope: Domain and Literature . 105 1.3 Overview . 106 1.4 Reading Guide . 106 2 Proof Engineering by Example 108 3 Why Proof Engineering Matters 111 3.1 Proof Engineering for Program Verification . 112 3.2 Proof Engineering for Other Domains . 117 3.3 Practical Impact . 124 4 Foundations and Trusted Bases 126 4.1 Proof Assistant Pre-History . 126 4.2 Proof Assistant Early History . 129 4.3 Proof Assistant Foundations . 130 4.4 Trusted Computing Bases of Proofs and Programs . 137 5 Between the Engineer and the Kernel: Languages and Automation 141 5.1 Styles of Automation . 142 5.2 Automation in Practice . 156 The version of record is available at: http://dx.doi.org/10.1561/2500000045 6 Proof Organization and Scalability 162 6.1 Property Specification and Encodings . -
Metamathematics in Coq Metamathematica in Coq (Met Een Samenvatting in Het Nederlands)
Metamathematics in Coq Metamathematica in Coq (met een samenvatting in het Nederlands) Proefschrift ter verkrijging van de graad van doctor aan de Universiteit Utrecht op gezag van de Rector Magnificus, Prof. dr. W.H. Gispen, ingevolge het besluit van het College voor Promoties in het openbaar te verdedigen op vrijdag 31 oktober 2003 des middags te 14:30 uur door Roger Dimitri Alexander Hendriks geboren op 6 augustus 1973 te IJsselstein. Promotoren: Prof. dr. J.A. Bergstra (Faculteit der Wijsbegeerte, Universiteit Utrecht) Prof. dr. M.A. Bezem (Institutt for Informatikk, Universitetet i Bergen) Voor Nelleke en Ole. Preface The ultimate arbiter of correctness is formalisability. It is a widespread view amongst mathematicians that correct proofs can be written out completely for- mally. This means that, after ‘unfolding’ the layers of abbreviations and con- ventions on which the presentation of a mathematical proof usually depends, the validity of every inference step should be completely perspicuous by a pre- sentation of this step in an appropriate formal language. When descending from the informal heat to the formal cold,1 we can rely less on intuition and more on formal rules. Once we have convinced ourselves that those rules are sound, we are ready to believe that the derivations they accept are correct. Formalis- ing reduces the reliability of a proof to the reliability of the means of verifying it ([60]). Formalising is more than just filling-in the details, it is a creative and chal- lenging job. It forces one to make decisions that informal presentations often leave unspecified. The search for formal definitions that, on the one hand, con- vincingly represent the concepts involved and, on the other hand, are convenient for formal proof, often elucidates the informal presentation. -
CHAPTER 8 Hilbert Proof Systems, Formal Proofs, Deduction Theorem
CHAPTER 8 Hilbert Proof Systems, Formal Proofs, Deduction Theorem The Hilbert proof systems are systems based on a language with implication and contain a Modus Ponens rule as a rule of inference. They are usually called Hilbert style formalizations. We will call them here Hilbert style proof systems, or Hilbert systems, for short. Modus Ponens is probably the oldest of all known rules of inference as it was already known to the Stoics (3rd century B.C.). It is also considered as the most "natural" to our intuitive thinking and the proof systems containing it as the inference rule play a special role in logic. The Hilbert proof systems put major emphasis on logical axioms, keeping the rules of inference to minimum, often in propositional case, admitting only Modus Ponens, as the sole inference rule. 1 Hilbert System H1 Hilbert proof system H1 is a simple proof system based on a language with implication as the only connective, with two axioms (axiom schemas) which characterize the implication, and with Modus Ponens as a sole rule of inference. We de¯ne H1 as follows. H1 = ( Lf)g; F fA1;A2g MP ) (1) where A1;A2 are axioms of the system, MP is its rule of inference, called Modus Ponens, de¯ned as follows: A1 (A ) (B ) A)); A2 ((A ) (B ) C)) ) ((A ) B) ) (A ) C))); MP A ;(A ) B) (MP ) ; B 1 and A; B; C are any formulas of the propositional language Lf)g. Finding formal proofs in this system requires some ingenuity. Let's construct, as an example, the formal proof of such a simple formula as A ) A. -
Experience Implementing a Performant Category-Theory Library in Coq
Experience Implementing a Performant Category-Theory Library in Coq Jason Gross, Adam Chlipala, and David I. Spivak Massachusetts Institute of Technology, Cambridge, MA, USA [email protected], [email protected], [email protected] Abstract. We describe our experience implementing a broad category- theory library in Coq. Category theory and computational performance are not usually mentioned in the same breath, but we have needed sub- stantial engineering effort to teach Coq to cope with large categorical constructions without slowing proof script processing unacceptably. In this paper, we share the lessons we have learned about how to repre- sent very abstract mathematical objects and arguments in Coq and how future proof assistants might be designed to better support such rea- soning. One particular encoding trick to which we draw attention al- lows category-theoretic arguments involving duality to be internalized in Coq's logic with definitional equality. Ours may be the largest Coq development to date that uses the relatively new Coq version developed by homotopy type theorists, and we reflect on which new features were especially helpful. Keywords: Coq · category theory · homotopy type theory · duality · performance 1 Introduction Category theory [14] is a popular all-encompassing mathematical formalism that casts familiar mathematical ideas from many domains in terms of a few unifying concepts. A category can be described as a directed graph plus algebraic laws stating equivalences between paths through the graph. Because of this spar- tan philosophical grounding, category theory is sometimes referred to in good humor as \formal abstract nonsense." Certainly the popular perception of cat- egory theory is quite far from pragmatic issues of implementation. -
A Toolchain to Produce Verified Ocaml Libraries
A Toolchain to Produce Verified OCaml Libraries Jean-Christophe Filliâtre, Léon Gondelman, Cláudio Lourenço, Andrei Paskevich, Mário Pereira, Simão Melo de Sousa, Aymeric Walch To cite this version: Jean-Christophe Filliâtre, Léon Gondelman, Cláudio Lourenço, Andrei Paskevich, Mário Pereira, et al.. A Toolchain to Produce Verified OCaml Libraries. 2020. hal-01783851v2 HAL Id: hal-01783851 https://hal.archives-ouvertes.fr/hal-01783851v2 Preprint submitted on 28 Jan 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A Toolchain to Produce Veried OCaml Libraries Jean-Christophe Filliâtre1, Léon Gondelman2, Cláudio Lourenço1, Andrei Paskevich1, Mário Pereira3, Simão Melo de Sousa4, and Aymeric Walch5 1 Université Paris-Saclay, CNRS, Inria, LRI, 91405, Orsay, France 2 Department of Computer Science, Aarhus University, Denmark 3 NOVA-LINCS, FCT-Univ. Nova de Lisboa, Portugal 4 NOVA-LINCS, Univ. Beira Interior, Portugal 5 École Normale Supérieure de Lyon, France Abstract. In this paper, we present a methodology to produce veri- ed OCaml libraries, using the GOSPEL specication language and the Why3 program verication tool. First, a formal behavioral specication of the library is written in OCaml/GOSPEL, in the form of an OCaml module signature extended with type invariants and function contracts. -
Deduction and Resolution
Lecture 12: Deduction and Resolution 1 Hilbert’s System Hilbert discovered a very elegant deductive system that is both sound and com- plete. His system uses only the connectives {¬, →}, which we know are an adequate basis. It has also been shown that each of the three axioms given below are necessary for the system to be sound and complete. Hilbert’s System consists of the following: • Three axioms (all are strongly sound): – A1: (p → (q → p)) Axiom of simplification. – A2: ((p → (q → r)) → ((p → q) → (p → r))) Frege’s axiom. – A3: ((¬p → q) → ((¬p → ¬q) → p)) Reductio ad absurdum. • Inference Rules: p,p→q – Modus Ponens: q (Strongly Sound) ϕ – Substitution: ϕ[θ] , where θ is a substitution (p → ψ). (Sound) The Substitution Inference Rule is shorthand for all sequences of the form hϕ, ϕ[θ]i. It is sometimes called a schema for generating inference rules. Note that in general, it is not the case that ϕ |= ϕ[θ], for example p 6|= q. However, in assignment 2, we showed that if |= ϕ, then |= ϕ[θ]. This is why this rule is sound but not strongly sound. Theorem 1. Hilbert’s system is sound, complete, and tractable. Proof. We prove each property separately. • Soundness: Since all axioms are strongly sound, and the two inference rules are sound, the whole system is sound. • Completeness: The proof of this property is fairly involved and thus it is outside the scope of the class. 1 + • Tractability: Given Γ ∈ Form and ϕ1, . , ϕn, is ϕ1, . , ϕn ∈ Deductions(Γ)? Clearly, < ϕ1 > is in Γ only if it is an axiom.