2018
DOI: 10.1017/s095679681700020x
|View full text |Cite
|
Sign up to set email alerts
|

Systematic identification and communication of type errors

Abstract: When type inference fails, it is often difficult to pinpoint the cause of the type error among many potential candidates. Generating informative messages to remove the type error is another difficult task due to the limited availability of type information. Over the last three decades many approaches have been developed to help debug type errors. However, most of these methods suffer from one or more of the following problems: (1) Being incomplete, they miss the real cause. (2) They cover many potential causes… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(1 citation statement)
references
References 38 publications
0
1
0
Order By: Relevance
“…Although Hazel supports only local type inference as of this writing, a system that uses ML-style type reconstruction to fill type holes statically, like GHC Haskell, would only be able to fill the first hole. Leaving the second hole unfilled is a parsimonious alternative to arbitrarily or heuristically choosing one of the possibilities and marking the other uses of x as ill-typed (see [Chen and Erwig 2018]).…”
Section: Example 4: Type Holes and Dynamic Type Errorsmentioning
confidence: 99%
“…Although Hazel supports only local type inference as of this writing, a system that uses ML-style type reconstruction to fill type holes statically, like GHC Haskell, would only be able to fill the first hole. Leaving the second hole unfilled is a parsimonious alternative to arbitrarily or heuristically choosing one of the possibilities and marking the other uses of x as ill-typed (see [Chen and Erwig 2018]).…”
Section: Example 4: Type Holes and Dynamic Type Errorsmentioning
confidence: 99%