DOCSLIB.ORG

Reactive Objects and Functional Programming

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Reactive Objects and Functional Programming A dissertation for the Ph.D. degree in Computing Science Reactive Objects and Functional Programming Johan Nordlander Department of Computing Science Chalmers University of Technology SE-412 96 G¨oteborg, Sweden G¨oteborg, May 1999 A dissertation for the Ph.D. Degree in Computing Science at Chalmers University of Technology Department of Computing Science Chalmers University of Technology SE-412 96 G¨oteborg, Sweden Reactive Objects and Functional Programming Johan Nordlander G¨oteborg 1999 ISBN 91-7197-823-2 Doktorsavhandlingar vid Chalmers Tekniska H¨ogskola Ny serie 1521 ISSN 0346-718X Abstract The construction of robust distributed and interactive software is still a chal- lenging task, despite the recent popularity-increase for languages that take ad- vanced programming concepts into the mainstream. Several problematic areas can be identified: most languages require the reactivity of a system to be man- ually upheld by careful avoidance of blocking operations; mathematical values often need to be encoded in terms of stateful objects or vice versa; concurrency is particularly tricky in conjunction with encapsulated software components; and static type safety is often compromised because of the lack of simultaneous support for both subtyping and polymorphism. This thesis presents a programming language, O'Haskell, that has been con- sciously designed with these considerations in mind. O'Haskell is defined by conservatively extending the purely functional language Haskell with the fol- lowing features: • A central structuring mechanism based on reactive objects, which unify the notions of objects and concurrent processes. Reactive objects are asynchronous, state-encapsulating servers whose purpose is to react to input messages; they cannot actively block execution or selectively filter their sources of input. • A monadic layer of object-based computational effects, which clearly sep- arates stateful objects from stateless values. Apart from higher-order functions and recursive data structures, the latter notion also includes first-class commands, object templates, and methods. • A safe, polymorphic type system with declared record and datatype sub- typing, supported by a powerful partial type inference algorithm. It is claimed that these features make O'Haskell especially well-adapted for the task of modern software construction. The thesis presents O'Haskell from both a practical and a theoretical per- spective. The practical contributions are a full implementation of the language, a number of non-trivial programming examples that illustrate the merits of re- active objects in a realistic context, and several reusable programming methods for such applications as graphical user interfaces, embedded controllers, and network protocols. The theoretical results serve to substantiate the informal claim made regarding usability, and include a provably sound polymorphic sub- typing system, soundness and partial completeness for the inference algorithm, a formal dynamic semantics, and a result that characterizes the conservative extension of a purely functional language with state and concurrency. Keywords: language design, functional programming, concurrency, reactive objects, polymorphic subtyping. Creativity is allowing yourself to make mistakes. Art is to know which ones to keep. | Scott Adams, creator of Dilbert. Acknowledgements Ten years ago Bj¨orn von Sydow, even then a renowned lecturer, and I, his under- graduate student, were having a discussion concerning the ideal programming language during a lunch-break at the Lule˚a Technical University. Although the discussion was conducted in rather vague terms, I still remember getting a very clear picture of what this ideal language should look like. When I now find myself in a position where I can sum up the many years of programming lan- guage research that have ultimately led to a finished thesis, I can only conclude that the result was there all the time! This was the language we were talking about, and it only makes me proud to give credit where credit is due | to my supervisor Bj¨orn von Sydow, who put me on the right track long before I knew I wanted to be a research student, and who has kept me on that track ever since. Thanks, Bj¨orn, for being such an enormous source of inspiration, for believing in me, and for letting me make the right mistakes! The Department of Computing Science at Chalmers has provided a very rich and stimulating research environment, and I would like to express my gratitude to its skilled administrative staff, and to all past and present colleagues with whom I have had so many joyful and educative encounters. I am particularly indebted to two very special friends and colleagues. Mag- nus Carlsson showed an early interest in my work (despite my ranting!), and soon became involved in it himself. Chapter 6 is based on work jointly per- formed with him. Magnus has also provided me with numerous comments on drafts of this thesis. Thomas Hallgren and I have had long discussions on type systems and almost every other subject as well, and he also provided the first full implementation of my subtype inference algorithm. Both Magnus and Thomas have moreover been an important part of my social life in G¨oteborg, and the only sensible way of acknowledging their influence on the making of this thesis is by saying: thanks for everything, brothers! It has been a pleasure! Thanks are also due to my supervision committee | Bengt Nordstr¨om, Dave Sands, and Thomas Johnson | for giving me useful comments on an earlier draft of the thesis and the work that has preceded it. The dissertation has also benefited from stimulating discussions with Lars Pareto, Lennart Augustsson, Simon Peyton Jones, Norman Ramsey, Rogardt Heldal, and Dan Synek, among others. I am moreover indebted to Fritz Henglein for patiently introducing me to the field of polymorphic subtyping, and to Philippas Tsigas and Marina Papatriantafilou for helping me sorting out the mysteries of self-stabilization. The commuting life I have been living during this period would not have been possible without the support of all good friends in G¨oteborg who have opened up their homes for me. To Johanna & Sven, Gunnel & Johan, Rauni & Pontus, Bj¨orn & Vero, Patrik & Lina, Janne & Camilla: my hearty thanks for the hospitality and the good company, and I hope you all feel that my family and I are always keeping our door open for you as well. Vivi-Anne Lundstr¨om's skilled eyes have helped me identify many weak spots in my English presentation, which I gratefully acknowledge. Vivi-Anne and Jack have also been a dependable source of encouragement over the years, as well as providers of invaluable help in numerous practical matters (especially during this last hectic period), and for that I am particularly grateful. A very special place in my heart is reserved for Siv Lundstr¨om and Owe Wikstr¨om, whom I count as my best friends, in the true meaning of the word. This work would not have been thinkable without their care and support, and I dedicate my thesis to them with pride. Finally, my most intimate thank you goes to Eva, my love and fellow-traveller in life. Much has changed since that distant day I left for Lule˚a to study and live in a caravan on a camp closed for the winter, but her love and unbroken faith in my capabilities has been a constant factor in my life. Now we share our home with three wonderful children, and to them I just want to say now that the \fairy-tale book" is finally written: Agnes, Charlott och Oskar | nu ska vi leka! This dissertation is partly based on previously published material. Chapter 5 is an extended version of [Nor98], and chapter 6 is based on the work reported in [NC97]. Some original thoughts underlying the thesis can also be found in [Nor95], although the technical material contained in that report should be considered superseded by [NC97] and the present work. Contents 1 Introduction 1 1.1 Background . 1 1.2 Thesis . 4 1.3 Reactive objects . 5 1.3.1 Object modeling . 5 1.3.2 Preserving reactivity . 7 1.3.3 Reactivity in interfaces . 8 1.3.4 Preserving message ordering . 9 1.4 Values vs. Objects . 10 1.4.1 Values in object-oriented languages . 10 1.4.2 Functional programming . 11 1.4.3 A monadic approach to objects . 12 1.5 Subtyping and polymorphism . 13 1.5.1 Subtyping and type inference . 15 1.5.2 Name inequivalence . 16 1.6 Related work . 16 1.6.1 Concurrency in functional languages . 16 1.6.2 Concurrent object-oriented languages . 18 1.6.3 Reactivity . 19 1.6.4 Polymorphic subtyping . 21 1.6.5 Name inequivalence . 22 1.7 Contributions . 23 1.8 Outline of the thesis . 24 2 Survey of O'Haskell 27 2.1 Haskell . 28 2.2 Records . 33 2.3 Subtyping . 35 2.3.1 Polymorphic subtype axioms . 36 2.3.2 Depth subtyping . 37 2.3.3 Restrictions on subtype axioms . 38 2.4 Automatic type inference . 39 2.5 Reactive objects . 42 2.5.1 Templates and methods . 42 vii viii CONTENTS 2.5.2 Procedures and commands . 43 2.5.3 A word about overloading . 44 2.5.4 Assignable local state . 45 2.5.5 The O monad . 46 2.5.6 Self . 47 2.5.7 Expressions vs. commands . 47 2.5.8 Subtyping in the O monad . 49 2.5.9 The main procedure . 50 2.5.10 Concurrency . 50 2.5.11 Reactivity . 51 2.6 Additional extensions . 52 2.6.1 Extended do-syntax . 52 2.6.2 Array updates . 53 2.6.3 Record stuffing . 54 2.7 What about inheritance? . 54 3 Examples 57 3.1 An interactive drawing program . 57 3.2 An AGV controller . 62 3.3 Sieve of Eratosthenes .
Load more

Recommended publications
  • GHC Reading Guide
    GHC Reading Guide - Exploring entrances and mental models to the source code - Takenobu T. Rev. 0.01.1 WIP NOTE: - This is not an official document by the ghc development team. - Please refer to the official documents in detail. - Don't forget “semantics”. It's very important. - This is written for ghc 9.0. Contents Introduction 1. Compiler - Compilation pipeline - Each pipeline stages - Intermediate language syntax - Call graph 2. Runtime system 3. Core libraries Appendix References Introduction Introduction Official resources are here GHC source repository : The GHC Commentary (for developers) : https://gitlab.haskell.org/ghc/ghc https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary GHC Documentation (for users) : * master HEAD https://ghc.gitlab.haskell.org/ghc/doc/ * latest major release https://downloads.haskell.org/~ghc/latest/docs/html/ * version specified https://downloads.haskell.org/~ghc/9.0.1/docs/html/ The User's Guide Core Libraries GHC API Introduction The GHC = Compiler + Runtime System (RTS) + Core Libraries Haskell source (.hs) GHC compiler RuntimeSystem Core Libraries object (.o) (libHsRts.o) (GHC.Base, ...) Linker Executable binary including the RTS (* static link case) Introduction Each division is located in the GHC source tree GHC source repository : https://gitlab.haskell.org/ghc/ghc compiler/ ... compiler sources rts/ ... runtime system sources libraries/ ... core library sources ghc/ ... compiler main includes/ ... include files testsuite/ ... test suites nofib/ ... performance tests mk/ ... build system hadrian/ ... hadrian build system docs/ ... documents : : 1. Compiler 1. Compiler Compilation pipeline 1. compiler The GHC compiler Haskell language GHC compiler Assembly language (native or llvm) 1. compiler GHC compiler comprises pipeline stages GHC compiler Haskell language Parser Renamer Type checker Desugarer Core to Core Core to STG STG to Cmm Assembly language Cmm to Asm (native or llvm) 1.
    [Show full text]
  • Haskell-Like S-Expression-Based Language Designed for an IDE
    Department of Computing Imperial College London MEng Individual Project Haskell-Like S-Expression-Based Language Designed for an IDE Author: Supervisor: Michal Srb Prof. Susan Eisenbach June 2015 Abstract The state of the programmers’ toolbox is abysmal. Although substantial effort is put into the development of powerful integrated development environments (IDEs), their features often lack capabilities desired by programmers and target primarily classical object oriented languages. This report documents the results of designing a modern programming language with its IDE in mind. We introduce a new statically typed functional language with strong metaprogramming capabilities, targeting JavaScript, the most popular runtime of today; and its accompanying browser-based IDE. We demonstrate the advantages resulting from designing both the language and its IDE at the same time and evaluate the resulting environment by employing it to solve a variety of nontrivial programming tasks. Our results demonstrate that programmers can greatly benefit from the combined application of modern approaches to programming tools. I would like to express my sincere gratitude to Susan, Sophia and Tristan for their invaluable feedback on this project, my family, my parents Michal and Jana and my grandmothers Hana and Jaroslava for supporting me throughout my studies, and to all my friends, especially to Harry whom I met at the interview day and seem to not be able to get rid of ever since. ii Contents Abstract i Contents iii 1 Introduction 1 1.1 Objectives ........................................ 2 1.2 Challenges ........................................ 3 1.3 Contributions ...................................... 4 2 State of the Art 6 2.1 Languages ........................................ 6 2.1.1 Haskell ....................................
    [Show full text]
  • A Formal Methodology for Deriving Purely Functional Programs from Z Specifications Via the Intermediate Specification Language Funz
    Louisiana State University LSU Digital Commons LSU Historical Dissertations and Theses Graduate School 1995 A Formal Methodology for Deriving Purely Functional Programs From Z Specifications via the Intermediate Specification Language FunZ. Linda Bostwick Sherrell Louisiana State University and Agricultural & Mechanical College Follow this and additional works at: https://digitalcommons.lsu.edu/gradschool_disstheses Recommended Citation Sherrell, Linda Bostwick, "A Formal Methodology for Deriving Purely Functional Programs From Z Specifications via the Intermediate Specification Language FunZ." (1995). LSU Historical Dissertations and Theses. 5981. https://digitalcommons.lsu.edu/gradschool_disstheses/5981 This Dissertation is brought to you for free and open access by the Graduate School at LSU Digital Commons. It has been accepted for inclusion in LSU Historical Dissertations and Theses by an authorized administrator of LSU Digital Commons. For more information, please contact [email protected]. INFORMATION TO USERS This manuscript has been reproduced from the microfilm master. UMI films the text directly from the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. H ie quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandardm argins, and improper alignment can adversely affect reproduction. In the unlikely, event that the author did not send UMI a complete manuscript and there are missing pages, these will be noted. Also, if unauthorized copyright material had to be removed, a note will indicate the deletion. Oversize materials (e.g., maps, drawings, charts) are reproduced by sectioning the original, beginning at the upper left-hand comer and continuing from left to right in equal sections with small overlaps.
    [Show full text]
  • The Logic of Demand in Haskell
    Under consideration for publication in J. Functional Programming 1 The Logic of Demand in Haskell WILLIAM L. HARRISON Department of Computer Science University of Missouri Columbia, Missouri RICHARD B. KIEBURTZ Pacific Software Research Center OGI School of Science & Engineering Oregon Health & Science University Abstract Haskell is a functional programming language whose evaluation is lazy by default. However, Haskell also provides pattern matching facilities which add a modicum of eagerness to its otherwise lazy default evaluation. This mixed or “non-strict” semantics can be quite difficult to reason with. This paper introduces a programming logic, P-logic, which neatly formalizes the mixed evaluation in Haskell pattern-matching as a logic, thereby simplifying the task of specifying and verifying Haskell programs. In P-logic, aspects of demand are reflected or represented within both the predicate language and its model theory, allowing for expressive and comprehensible program verification. 1 Introduction Although Haskell is known as a lazy functional language because of its default eval- uation strategy, it contains a number of language constructs that force exceptions to that strategy. Among these features are pattern-matching, data type strictness annotations and the seq primitive. The semantics of pattern-matching are further enriched by irrefutable pattern annotations, which may be embedded within pat- terns. The interaction between Haskell’s default lazy evaluation and its pattern- matching is surprisingly complicated. Although it offers the programmer a facility for fine control of demand (Harrison et al., 2002), it is perhaps the aspect of the Haskell language least well understood by its community of users. In this paper, we characterize the control of demand first in a denotational semantics and then in a verification logic called “P-logic”.
    [Show full text]
  • Functional Baby Talk: Analysis of Code Fragments from Novice Haskell Programmers
    Functional Baby Talk: Analysis of Code Fragments from Novice Haskell Programmers Jeremy Singer and Blair Archibald School of Computing Science University of Glasgow UK [email protected] [email protected] What kinds of mistakes are made by novice Haskell developers, as they learn about functional pro- gramming? Is it possible to analyze these errors in order to improve the pedagogy of Haskell? In 2016, we delivered a massive open online course which featured an interactive code evaluation en- vironment. We captured and analyzed 161K interactions from learners. We report typical novice developer behavior; for instance, the mean time spent on an interactive tutorial is around eight min- utes. Although our environment was restricted, we gain some understanding of Haskell novice er- rors. Parenthesis mismatches, lexical scoping errors and do block misunderstandings are common. Finally, we make recommendations about how such beginner code evaluation environments might be enhanced. 1 Introduction The Haskell programming language [14] has acquired a reputation for being difficult to learn. In his presentation on the origins of Haskell [23] Peyton Jones notes that, according to various programming language popularity metrics, Haskell is much more frequently discussed than it is used for software implementation. The xkcd comic series features a sarcastic strip on Haskell’s side-effect free property [21]. Haskell code is free from side-effects ‘because no-one will ever run it.’ In 2016, we ran the first instance of a massive open online course (MOOC) at Glasgow, providing an introduction to functional programming in Haskell. We received many items of learner feedback that indicated difficulty in learning Haskell.
    [Show full text]
  • Haskell As a Higher Order Structural Hardware Description Language
    Haskell as a higher order structural hardware description language Master's thesis by Matthijs Kooijman December 9, 2009 Committee: Dr. Ir. Jan Kuper Ir. Marco Gerards Ir. Bert Molenkamp Dr. Ir. Sabih Gerez Computer Architecture for Embedded Systems Faculty of EEMCS University of Twente Abstract Functional hardware description languages have been around for a while, but never saw adoption on a large scale. Even though advanced features like higher order functions and polymorphism could enable very natural parametrization of hardware descriptions, the conventional hardware description languages VHDL and Verilog are still most widely used. Cλash is a new functional hardware description language using Haskell's syntax and semantics. It allows structurally describing synchronous hardware, using normal Haskell syntax combined with a selection of built-in functions for operations like addition or list operations. More complex constructions like higher order functions and polymorphism are fully supported. Cλash supports stateful descriptions through explicit descriptions of a function's state. Every function accepts an argument containing its current state and returns its updated state as a part of its result. This means every function is called exactly once for each cycle, limiting Cλash to synchronous systems with a single clock domain. A prototype compiler for Cλash has been implemented that can generate an equivalent VHDL description (using mostly structural VHDL). The prototype uses the front-end (parser, type-checker, desugarer) ofthe existing GHC Haskell compiler. This front-end generates a Core version of the description, which is a very small typed functional language. A normalizing system of transformations brings this Core version into a normal form that has any complex parts (higher order functions, polymorphism, complex nested structures) removed.
    [Show full text]
  • A Proxima-Based Haskell IDE
    Thesis for the degree of Master of Science A Proxima-based Haskell IDE Gerbo Engels October 2008 INF/SCR-07-93 Supervisor: Center for Software Technology prof. dr. S. Doaitse Swierstra Dept. of Information and Computing Sciences Universiteit Utrecht Daily supervisor: Utrecht, The Netherlands dr. Martijn M. Schrage Abstract Proxima is a generic presentation-oriented editor for structured documents, in which a graphical presentation of the document can be edited directly (WYSIWYG editing), resulting in changes in the underlying structure of the document. Proxima understands the document structure and it supports direct edit operations on the document structure as well. A Proxima instantiation uses a parser to get the document structure; modern compilers have parsers as well, which may be accessible through an API. Using the parser of an external compiler as the Proxima parser saves one from writing a new parser. Furthermore, the parse tree of a com- piler can contain extra information that is useful to display in an editor, such as type information of a Haskell compiler in a Haskell source code editor. This thesis aims to use the parser of an external compiler as the Proxima parser. We identify and solve problems that arise when using the parser of an external compiler as the Proxima parser, and two Haskell editors are developed as Proxima instantiations that use the parser of GHC or EHC respectively. i ii Contents 1 Introduction 1 1.1 Thesis Overview.........................................2 I The State of the World3 2 Existing Haskell Editors and IDE’s5 2.1 Visual Haskell...........................................6 2.2 Eclipse Plug-in...........................................7 2.3 Haskell Editors Written in Haskell...............................8 2.4 Other Editors or Tools.....................................
    [Show full text]
  • Haskell High Performance Programming Table of Contents
    Haskell High Performance Programming Table of Contents Haskell High Performance Programming Credits About the Author About the Reviewer www.PacktPub.com eBooks, discount offers, and more Why subscribe? Preface What this book covers What you need for this book Who this book is for Conventions Reader feedback Customer support Downloading the example code Downloading the color images of this book Errata Piracy Questions 1. Identifying Bottlenecks Meeting lazy evaluation Writing sum correctly Weak head normal form Folding correctly Memoization and CAFs Constant applicative form Recursion and accumulators The worker/wrapper idiom Guarded recursion Accumulator parameters Inspecting time and space usage Increasing sharing and minimizing allocation Compiler code optimizations Inlining and stream fusion Polymorphism performance Partial functions Summary 2. Choosing the Correct Data Structures Annotating strictness and unpacking datatype fields Unbox with UNPACK Using anonymous tuples Performance of GADTs and branching Handling numerical data Handling binary and textual data Representing bit arrays Handling bytes and blobs of bytes Working with characters and strings Using the text library Builders for iterative construction Builders for strings Handling sequential data Using difference lists Difference list performance Difference list with the Writer monad Using zippers Accessing both ends fast with Seq Handling tabular data Using the vector package Handling sparse data Using the containers package Using the unordered-containers package Ephemeral
    [Show full text]
  • Trace-Based Just-In-Time Compilation for Lazy Functional Programming Languages
    Trace-based Just-in-time Compilation for Lazy Functional Programming Languages Thomas Schilling School of Computing University of Kent at Canterbury A thesis submitted for the degree of Doctor of Philosophy April 2013 i Abstract This thesis investigates the viability of trace-based just-in-time (JIT) compilation for optimising programs written in the lazy functional programming language Haskell. A trace-based JIT compiler optimises only execution paths through the program, which is in contrast to method-based compilers that optimise complete functions at a time. The potential advantages of this approach are shorter compilation times and more natural interprocedural optimisation. Trace-based JIT compilers have previously been used successfully to optimise programs written in dynamically typed languages such as JavaScript, Python, or Lua, but also statically typed languages like Java or the Common Language Runtime (CLR). Lazy evalu- ation poses implementation challenges similar to those of dynamic languages, so trace-based JIT compilation promises to be a viable ap- proach. In this thesis we focus on program performance, but having a JIT compiler available can simplify the implementation of features like runtime inspection and mobile code. We implemented Lambdachine, a trace-based JIT compiler which im- plements most of the pure subset of Haskell. We evaluate Lamb- dachine's performance using a set of micro-benchmarks and a set of larger benchmarks from the \spectral" category of the Nofib bench- mark suite. Lambdachine's performance (excluding garbage collection overheads) is generally about 10 to 20 percent slower than GHC on statically optimised code. We identify the two main causes for this slow-down: trace selection and impeded heap allocation optimisations due to unnecessary thunk updates.
    [Show full text]
  • Introduction to Haskell
    Advanced Topics in Programming Languages Lecture 2 - Introduction to Haskell Ori Bar El Maxim Finkel 01/11/17 1 History Haskell is a lazy, committee designed, pure functional programming language that started development in the late 1980’s. Haskell derives its name from Haskell Curry, a mathematician and logician. The goals of the Haskell language were formally defined by its designers, and they stated that Haskell should: 1. Be suitable for teaching, research, and applications, including building 2. Be completely described via the publication of a formal syntax and se- mantics. 3. Be freely available. 4. Be usable as a basis for further language research. 5. Be based on ideas that enjoy a wide consensus. 6. Reduce unnecessary diversity in functional programming languages. Development of the language began shortly after the 1988 meeting, but it was not until April 1, 1990 that the first working version of Haskell, Haskell 1.0, was released. From 1990 to 1999 many incremental versions of Haskell were released and in 1999 the Haskell Committee decided that a formalized and stable version of the language needed to be released. They decided to call this standard version of the language Haskell 98. The reasoning behind creating a Haskell standard was so the language could be used in teaching environments and books could be written about it. Haskell 98 did not fully stabilize until 2002. Haskell recently released a new standardized version called Haskell 2010. This update includes all the changes in the language since 2002 repackaged with up-to-date documentation in the newest version of the Haskell Report.
    [Show full text]
  • Csci 450: Org. of Programming Languages Basic Haskell Functional Programming
    CSci 450: Org. of Programming Languages Basic Haskell Functional Programming H. Conrad Cunningham 26 October 2017 Contents 2 Basic Haskell Functional Programming 2 2.1 Chapter Introduction . 2 2.2 Defining Our First Haskell Functions . 2 2.2.1 Factorial function specification . 2 2.2.2 Factorial function using if-then-else: fact1 . 3 2.2.3 Factorial function using guards: fact2 ........... 5 2.2.4 Factorial function using pattern matching: fact3 and fact4 6 2.2.5 Factorial function using a built-in library function: fact5 7 2.3 Using the Glasgow Haskell Compiler (GHC) . 7 2.4 Surveying the Basic Types . 10 2.4.1 Integers: Int and Integer . 10 2.4.2 Floating point numbers: Float and Double . 10 2.4.3 Booleans: Bool ........................ 11 2.4.4 Characters: Char ....................... 11 2.4.5 Functions: t1 -> t2 ..................... 11 2.4.6 Tuples: (t1,t2,...,tn) . 12 2.4.7 Lists: [t] ........................... 13 2.4.8 Strings: String ........................ 13 2.5 Using Top-Down Stepwise Refinement . 14 2.5.1 Developing a square root package . 14 2.5.2 Making the package a Haskell module . 16 2.5.3 Top-down stepwise refinement . 16 2.6 Using Data Abstraction . 17 2.6.1 Rational number arithmetic . 17 2.6.2 Rational number data representation . 19 2.6.3 Modularization . 21 2.6.4 Alternative rational number data representation . 22 2.7 Modular Design and Programming . 25 2.7.1 Information-hiding modules . 25 2.7.2 Interfaces . 26 1 2.7.3 Haskell information-hiding modules . 26 2.7.4 Invariants .
    [Show full text]
  • Ready, Set, Verify! Applying Hs-To-Coq to Real-World Haskell Code
    Ready, Set, Verify! Applying hs-to-coq to real-world Haskell code JOACHIM BREITNER, University of Pennsylvania, USA ANTAL SPECTOR-ZABUSKY, University of Pennsylvania, USA YAO LI, University of Pennsylvania, USA CHRISTINE RIZKALLAH, University of New South Wales, Australia JOHN WIEGLEY, BAE Systems, USA STEPHANIE WEIRICH, University of Pennsylvania, USA Good tools can bring mechanical verification to programs written in mainstream functional languages. Weuse hs-to-coq to translate significant portions of Haskell’s containers library into Coq, and verify it against specifications that we derive from a variety of sources including type class laws, the library’s testsuite,and interfaces from Coq’s standard library. Our work shows that it is feasible to verify mature, widely-used, highly optimized, and unmodified Haskell code. We also learn more about the theory of weight-balanced trees, extend hs-to-coq to handle partiality, and – since we found no bugs – attest to the superb quality of well-tested functional code. CCS Concepts: • Software and its engineering → Software verification; Additional Key Words and Phrases: Coq, Haskell, verification 1 INTRODUCTION What would it take to tempt functional programmers to verify their code? Certainly, better tools would help. We see that functional programmers who use dependently- typed languages or proof assistants, such as Coq [The Coq development team 2016], Agda [Bove et al. 2009], Idris [Brady 2017], and Isabelle [Nipkow et al. 2002], do verify their code, since their tools allow it. However, adopting these platforms means rewriting everything from scratch. What about the verification of existing code, such as libraries written in mature languages like Haskell? Haskell programmers can reach for LiquidHaskell [Vazou et al.
    [Show full text]