A complement to blame

Philip Wadler

doi:10.4230/LIPIcs.SNAPL.2015.309

A complement to blame

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

Abstract / Description of output

Contracts, gradual typing, and hybrid typing all permit less-precisely typed and more-precisely typed code to interact. Blame calculus encompasses these, and guarantees blame safety: blame for type errors always lays with less-precisely typed code. This paper serves as a complement to the literature on blame calculus: it elaborates on motivation, comments on the reception of the work, critiques some work for not properly attending to blame, and looks forward to applications. No knowledge of contracts, gradual typing, hybrid typing, or blame calculus is assumed.

Original language	English
Title of host publication	1st Summit on Advances in Programming Languages (SNAPL 2015)
Editors	Thomas Ball, Rastislav Bodik, Shriram Krishnamurthi, BEnjamin S. Lerner, Greg Morrisett
Publisher	Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik, Germany
Pages	309-320
Number of pages	12
ISBN (Electronic)	978-3-939897-80-4
DOIs	https://doi.org/10.4230/LIPIcs.SNAPL.2015.309
Publication status	Published - 2015

Publication series

Name	Leibniz International Proceedings in Informatics (LIPIcs)
Publisher	Schloss Dagstuhl--Leibniz-Zentrum fuer Informatik
Volume	32
ISSN (Print)	1868-8969

Access to Document

10.4230/LIPIcs.SNAPL.2015.309

complementFinal published version, 468 KBLicence: Creative Commons: Attribution (CC-BY)

http://drops.dagstuhl.de/opus/volltexte/2015/5033/Licence: Creative Commons: Attribution (CC-BY)

From Data Types to Session Types - A Basis for Concurrency and Distribution
Wadler, P.
EPSRC
20/05/13 → 19/11/20
Project: Research

Cite this

Wadler, P. (2015). A complement to blame. In T. Ball, R. Bodik, S. Krishnamurthi, BE. S. Lerner, & G. Morrisett (Eds.), 1st Summit on Advances in Programming Languages (SNAPL 2015) (pp. 309-320). (Leibniz International Proceedings in Informatics (LIPIcs); Vol. 32). Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik, Germany. https://doi.org/10.4230/LIPIcs.SNAPL.2015.309

@inproceedings{d2dd17d0a88349b4aa3396e694c9be50,

title = "A complement to blame",

abstract = "Contracts, gradual typing, and hybrid typing all permit less-precisely typed and more-precisely typed code to interact. Blame calculus encompasses these, and guarantees blame safety: blame for type errors always lays with less-precisely typed code. This paper serves as a complement to the literature on blame calculus: it elaborates on motivation, comments on the reception of the work, critiques some work for not properly attending to blame, and looks forward to applications. No knowledge of contracts, gradual typing, hybrid typing, or blame calculus is assumed.",

author = "Philip Wadler",

note = "Date of Acceptance: 20/02/2015",

year = "2015",

doi = "10.4230/LIPIcs.SNAPL.2015.309",

language = "English",

series = "Leibniz International Proceedings in Informatics (LIPIcs)",

publisher = "Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik, Germany",

pages = "309--320",

editor = "Thomas Ball and Rastislav Bodik and Shriram Krishnamurthi and Lerner, {BEnjamin S.} and Greg Morrisett",

booktitle = "1st Summit on Advances in Programming Languages (SNAPL 2015)",

}

A complement to blame. / Wadler, Philip.
1st Summit on Advances in Programming Languages (SNAPL 2015). ed. / Thomas Ball; Rastislav Bodik; Shriram Krishnamurthi; BEnjamin S. Lerner; Greg Morrisett. Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik, Germany, 2015. p. 309-320 (Leibniz International Proceedings in Informatics (LIPIcs); Vol. 32).

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

TY - GEN

T1 - A complement to blame

AU - Wadler, Philip

N1 - Date of Acceptance: 20/02/2015

PY - 2015

Y1 - 2015

N2 - Contracts, gradual typing, and hybrid typing all permit less-precisely typed and more-precisely typed code to interact. Blame calculus encompasses these, and guarantees blame safety: blame for type errors always lays with less-precisely typed code. This paper serves as a complement to the literature on blame calculus: it elaborates on motivation, comments on the reception of the work, critiques some work for not properly attending to blame, and looks forward to applications. No knowledge of contracts, gradual typing, hybrid typing, or blame calculus is assumed.

AB - Contracts, gradual typing, and hybrid typing all permit less-precisely typed and more-precisely typed code to interact. Blame calculus encompasses these, and guarantees blame safety: blame for type errors always lays with less-precisely typed code. This paper serves as a complement to the literature on blame calculus: it elaborates on motivation, comments on the reception of the work, critiques some work for not properly attending to blame, and looks forward to applications. No knowledge of contracts, gradual typing, hybrid typing, or blame calculus is assumed.

U2 - 10.4230/LIPIcs.SNAPL.2015.309

DO - 10.4230/LIPIcs.SNAPL.2015.309

M3 - Conference contribution

T3 - Leibniz International Proceedings in Informatics (LIPIcs)

SP - 309

EP - 320

BT - 1st Summit on Advances in Programming Languages (SNAPL 2015)

A2 - Ball, Thomas

A2 - Bodik, Rastislav

A2 - Krishnamurthi, Shriram

A2 - Lerner, BEnjamin S.

A2 - Morrisett, Greg

PB - Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik, Germany

ER -

A complement to blame

Abstract / Description of output

Publication series

Access to Document

Fingerprint

Projects

From Data Types to Session Types - A Basis for Concurrency and Distribution

Cite this