(Enter summary)
Abstract: This paper gives the outline of a type-deriver that can explain its reasoning in
response to questions. First, we should be able to point at a subexpression and
ask what type it has; such an interface has been implemented by Jan Sparud at
Chalmers [6]. Second, we should be able to ask why a certain type has been derived;
such a type-deriver has been implemented by Mitchell Wand [7]. When an error
is detected, Wand's type-deriver suggests a number of possible error sites. One of
these should be... (Update)
Context of citations to this paper: More
...a user still needs to remember all the steps of the inference. Furthermore, explanations tend to be lengthy and repetitive. Rittri [14] has suggested an interactive type debugger which can be tied to any inference algorithm. This would allow programmers to explore the type of...
.... that from a type error message it is often hard to deduce the actual cause of the error and understand it [1, 2, 3, 4, 9, 10, 17, 19, 20, 21, 22, 23, 24, 25, 26]. Consider the following tiny Haskell program [16] f xs ys = map toUpper) xs ys Permission to make...
Cited by: More
Improving Polymorphic Type Explanations - Yang (2001)
(Correct)
Explaining Polymorphic Types - Jun, Michaelson, Trinder (2002)
(Correct)
Repairing Type Errors in Functional Programs - McAdam (2001)
(Correct)
Active bibliography (related documents): More All
0.1: Diagnosis of Ill-typed Programs - Choppella, Haynes (1995)
(Correct)
0.1: Interactive Type Debugging - McAdam (1998)
(Correct)
0.1: Compositional Explanation of Types and Algorithmic Debugging of.. - Chitil (2001)
(Correct)
System load high. Please wait...
Timeout. Please try your query later.
Similar documents based on text: More All
0.1: Retrieving Library Identifiers via Equational Matching of Types - Rittri (1992)
(Correct)
0.1: Learning to Solve Complex Tasks by Reinforcement: A New.. - Martin, Cortés (1995)
(Correct)
0.1: Retrieving Library Functions By Unifying Types Modulo Linear.. - Rittri (1992)
(Correct)
Related documents from co-citation: More All
7: Finding the source of type errors (context) - Wand - 1986
7: A theory of type polymorphism in programming (context) - Milner - 1978
6: Interactive programming environment for ML
- Rideau, Thery - 1997
BibTeX entry: (Update)
M. Rittri. Finding the source of type errors interactively. Technical report, Department of Computer Science, Chalmers University of Technology, Sweden, 1993. http://citeseer.ist.psu.edu/rittri93finding.html More
@misc{ rittri93finding,
author = "M. Rittri",
title = "Finding the source of type errors interactively",
text = "M. Rittri. Finding the source of type errors interactively. Technical report,
Department of Computer Science, Chalmers University of Technology, Sweden,
1993.",
year = "1993",
url = "citeseer.ist.psu.edu/rittri93finding.html" }
Citations (may not include all citations):
343
Principal type-schemes for functional programs (context) - Damas, Milner - 1982 DBLP
45
Finding the source of type errors (context) - Wand - 1986 ACM DBLP
35
Partial type inference for untyped functional programs (context) - Gomard - 1990 ACM DBLP
22
A maximum-flow approach to anomaly isolation in unification-.. (context) - Johnson, Walz - 1986 ACM DBLP
15
An explanation based polymorphic type checker for Standard M.. (context) - Soosaipillai - 1990
1
personal communication (context) - Sparud
1
Presented at the annual winter workshop (context) - Carlsson, messages et al. - 1991
The graph only includes citing articles where the year of publication is known.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC