Unlike traditional static type checking, the type system in the Dart programming language is unsound by design, even for fully annotated programs. The rationale has been that this allows compile-time detection of likely errors and enables code completion in integrated development environments, without being restrictive on programmers.
Despite unsoundness, judicious use of type annotations can ensure useful properties of the runtime behavior of Dart programs. We present a formal model of a core of Dart with a focus on its type system, which allows us to elucidate the causes of unsoundness. Our main contribution is a characterization of message-safe programs and a theorem stating that such programs will never encounter ‘message not understood’ errors at runtime. Message safety is less restrictive than traditional type soundness, and we argue that it forms a natural intermediate point between dynamically typed and statically typed Dart programs.
Tue 27 Oct Times are displayed in time zone: Eastern Time (US & Canada) change
|10:30 - 10:52|
|A Formalization of Typed Lua|
|10:52 - 11:15|
|Gradual Certified Programming in Coq|
|11:15 - 11:37|
|Message Safety in Dart|
|11:37 - 12:00|
|Control-Flow Analysis of Dynamic Languages via Pointer Analysis|