When and How Java Developers Give Up Static Type Safety
Decanato - Facoltà di scienze informatiche
Data: / -
USI Lugano Campus, room SI-003, Informatics building (Via G. Buffi 13)
You are cordially invited to attend the PhD Dissertation Defense of Luis Mastrangelo on Thursday June 13th, 2019 at 14:30 in room SI-003 (Informatics building).
The main goal of a static type system is to prevent certain kinds of errors from happening at run time. A type system is formulated as a set of constraints that gives any expression or term in a program a well-defined type. Besides detecting these kinds of errors, a static type system can be an invaluable maintenance tool, can be useful for documentation purposes, and can aid in generating more efficient machine code. However, there are situations when the developer has more information about the program that is too complex to explain in terms of typing constraints. To that end, programming languages often provide mechanisms that make the typing constraints less strict to permit more programs to be valid, at the expense of causing more errors at run time. These mechanisms are essentially two: Unsafe Intrinsics and Reflective Capabilities. We want to understand how and when developers give up these static constraints. This knowledge can be useful as: a) a recommendation for current and future language designers to make informed decisions, b) a reference for tool builders, e.g., by providing more precise or new refactoring analyses, c) a guide for researchers to test new language features, or to carry out controlled programming experiments, and d) a guide for developers for better practices. In this dissertation, we focus on the Unsafe API and cast operator---a subset of unsafe intrinsics and reflective capabilities respectively---in Java. We report two empirical studies to understand how these mechanisms---Unsafe API and cast operator---are used by Java developers when the static type system becomes too strict. We have devised usage patterns for both the Unsafe API and cast operator. Usage patterns are recurrent programming idioms to solve a specific issue. We believe that having usage patterns can help us to better categorize use cases and thus understand how those features are used.
- Prof. Matthias Hauswirth, Università della Svizzera italiana, Switzerland (Research Advisor)
- Prof. Nate Nystrom, Università della Svizzera italiana, Switzerland (Research co-Advisor)
- Prof. Gabriele Bavota, Università della Svizzera italiana, Switzerland (Internal Member)
- Prof. Antonio Carzaniga, Università della Svizzera italiana, Switzerland (Internal Member)
- Prof. Hridesh Rajan, Iowa State University, USA (External Member)
- Prof. Jan Vitek, Northeastern University, USA -and- Czech Technical University, Czech Republic (External Member)