Type safety analysis for dart

Thomas S. Heinze; Anders Møller; Fabio Strocco

doi:10.1145/2989225.2989226

Type safety analysis for dart

Thomas S. Heinze, Anders Møller, Fabio Strocco

Department of Computer Science

Research output: Contribution to book/anthology/report/proceeding › Article in proceedings › Research › peer-review

7 Citations (Scopus)

175 Downloads (Pure)

Abstract

Optional typing is traditionally viewed as a compromise between static and dynamic type checking, where code without type annotations is not checked until runtime. We demonstrate that optional type annotations in Dart programs can be integrated into a flow analysis to provide static type safety guarantees both for annotated and non-annotated parts of the code. We explore two approaches: one that uses type annotations for filtering, and one that uses them as specifications. What makes this particularly challenging for Dart is that its type system is unsound even for fully annotated code. Experimental results show that the technique is remarkably effective, even without context sensitivity: 99:3% of all property lookup operations are reported type safe in a collection of benchmark programs.

Original language	English
Title of host publication	DLS 2016 - Proceedings of the 12th Symposium on Dynamic Languages
Editors	Roberto Ierusalimschy
Number of pages	12
Publisher	Association for Computing Machinery
Publication date	1 Nov 2016
Pages	1-12
ISBN (Print)	978-1-4503-4445-6
ISBN (Electronic)	9781450344456
DOIs	https://doi.org/10.1145/2989225.2989226
Publication status	Published - 1 Nov 2016
Event	SPLASH 2016: Systems, Programming, and Applications - Amsterdam, Netherlands Duration: 30 Oct 2016 → 4 Nov 2016 http://2016.splashcon.org/

Conference

Conference	SPLASH 2016
Country/Territory	Netherlands
City	Amsterdam
Period	30/10/2016 → 04/11/2016
Internet address	http://2016.splashcon.org/

Keywords

Optional types
Static analysis
Type systems

Access to Document

10.1145/2989225.2989226

4,1Accepted manuscript, 1.12 MB

http://cs.au.dk/~amoeller/papers/safedart/

Cite this

@inproceedings{e1ae74c84f59430fa7b69961cb73e799,

title = "Type safety analysis for dart",

abstract = "Optional typing is traditionally viewed as a compromise between static and dynamic type checking, where code without type annotations is not checked until runtime. We demonstrate that optional type annotations in Dart programs can be integrated into a flow analysis to provide static type safety guarantees both for annotated and non-annotated parts of the code. We explore two approaches: one that uses type annotations for filtering, and one that uses them as specifications. What makes this particularly challenging for Dart is that its type system is unsound even for fully annotated code. Experimental results show that the technique is remarkably effective, even without context sensitivity: 99:3% of all property lookup operations are reported type safe in a collection of benchmark programs.",

keywords = "Optional types, Static analysis, Type systems",

author = "Heinze, {Thomas S.} and Anders M{\o}ller and Fabio Strocco",

year = "2016",

month = nov,

day = "1",

doi = "10.1145/2989225.2989226",

language = "English",

isbn = "978-1-4503-4445-6",

pages = "1--12",

editor = "Roberto Ierusalimschy",

booktitle = "DLS 2016 - Proceedings of the 12th Symposium on Dynamic Languages",

publisher = "Association for Computing Machinery",

address = "United States",

note = "SPLASH 2016 ; Conference date: 30-10-2016 Through 04-11-2016",

url = "http://2016.splashcon.org/",

}

TY - GEN

T1 - Type safety analysis for dart

AU - Heinze, Thomas S.

AU - Møller, Anders

AU - Strocco, Fabio

PY - 2016/11/1

Y1 - 2016/11/1

N2 - Optional typing is traditionally viewed as a compromise between static and dynamic type checking, where code without type annotations is not checked until runtime. We demonstrate that optional type annotations in Dart programs can be integrated into a flow analysis to provide static type safety guarantees both for annotated and non-annotated parts of the code. We explore two approaches: one that uses type annotations for filtering, and one that uses them as specifications. What makes this particularly challenging for Dart is that its type system is unsound even for fully annotated code. Experimental results show that the technique is remarkably effective, even without context sensitivity: 99:3% of all property lookup operations are reported type safe in a collection of benchmark programs.

AB - Optional typing is traditionally viewed as a compromise between static and dynamic type checking, where code without type annotations is not checked until runtime. We demonstrate that optional type annotations in Dart programs can be integrated into a flow analysis to provide static type safety guarantees both for annotated and non-annotated parts of the code. We explore two approaches: one that uses type annotations for filtering, and one that uses them as specifications. What makes this particularly challenging for Dart is that its type system is unsound even for fully annotated code. Experimental results show that the technique is remarkably effective, even without context sensitivity: 99:3% of all property lookup operations are reported type safe in a collection of benchmark programs.

KW - Optional types

KW - Static analysis

KW - Type systems

UR - http://www.scopus.com/inward/record.url?scp=85002157865&partnerID=8YFLogxK

U2 - 10.1145/2989225.2989226

DO - 10.1145/2989225.2989226

M3 - Article in proceedings

AN - SCOPUS:85002157865

SN - 978-1-4503-4445-6

SP - 1

EP - 12

BT - DLS 2016 - Proceedings of the 12th Symposium on Dynamic Languages

A2 - Ierusalimschy, Roberto

PB - Association for Computing Machinery

T2 - SPLASH 2016

Y2 - 30 October 2016 through 4 November 2016

ER -

Type safety analysis for dart

Abstract

Conference

Keywords

Access to Document

Other files and links

Fingerprint

Cite this