xOur data center is currently experiencing power issues. Our colleagues are working hard to resolve the issue and keep downtime to a minimum.
Write a Blog >>
ICFP 2016
Sun 18 - Sat 24 September 2016 Nara, Japan
Sun 18 Sep 2016 17:00 - 17:30 at Conference Room 5 - 5 Chair(s): Atsushi Igarashi

It is not always easy to correct a type error especially for novice programmers. When a type error occurs, the compiler shows a type error message, but often, it does not show the true cause of the type error. Why? Because it is impossible in general. Without knowing the intention of the programmer, the compiler cannot choose a single cause among multiple possible causes of the type error.

To locate the true cause of a type error, we have built an interactive type debugger for OCaml that incorporates programmer’s intention. When a type error occurs, the type debugger asks a series of questions to the programmer. By correctly answering these questions, we are lead to the true source of the type error.

In this talk, I will first introduce the principle of the type debugger and show how a simple but crucial idea leads to a practicable type debugger. I then describe requirements and challenges for such a tool to be effective in the real use cases, such as in a classroom.

(plmw16.pdf)1.2MiB

Sun 18 Sep

Displayed time zone: Osaka, Sapporo, Tokyo change

17:00 - 18:00
5PLMW at Conference Room 5
Chair(s): Atsushi Igarashi Kyoto University
17:00
30m
Talk
Principle and Practice of OCaml Type Debugger
PLMW
Kenichi Asai Ochanomizu University
File Attached
17:30
30m
Talk
Unaccustomed as I am to public speaking
PLMW
John Hughes Chalmers University of Technology