Providing better supports for debugging type errors has been an active research area in the last three decades. Numerous approaches from different perspectives have been developed. Most approaches work well under certain conditions only, for example, when type errors are caused by single leaves and when type annotations are correct. However, the research community is still unaware which conditions hold in practice and what the real debugging situations look like. We address this problem with a study of 4 program datasets, which were written in different years, using different languages, by students with different backgrounds, and were of diverse sizes. They include more than 60,000 programs, among which more than 3,900 are ill typed. We investigated all the ill-typed programs, and our results indicate that current error debugging support is far from sufficient in practice since only about 30% of all type errors were caused by single leaves. Our study also provides many insights about the debugging behaviors of students in functional programming, which could be exploited for developing more effective error debuggers.
Fri 27 OctDisplayed time zone: Tijuana, Baja California change
13:30 - 15:00
|Deadlock Avoidance in Parallel Programs with Futures: Why Parallel Tasks Should Not Wait for Strangers
Tiago Cogumbreiro Rice University, Rishi Surendran Rice University, USA, Francisco Martins LaSIGE, University of Lisbon, Vivek Sarkar Rice University, USA, Vasco T. Vasconcelos University of Lisbon, Portugal, Max Grossman Rice University, USADOI
|Detecting Argument Selection Defects
Andrew Rice University of Cambridge, UK, Eddie Aftandilian Google, Ciera Jaspan Google, Emily Johnston Google, Michael Pradel TU Darmstadt, Yulissa Arroyo-Paredes Columbia University, USADOI
|How Type Errors Were Fixed and What Students Did?
|Learning User Friendly Type-Error Messages
Baijun Wu University of Louisiana at Lafayette, USA, John Peter Campora ULL Lafayette, Sheng Chen ULL LafayetteDOI