Counter-factual typing for debugging type errors

DOI10.1145/2535838.2535863MaRDI QIDQ5408451zbMATH OpenOpenAlexWikidataFDO

Authors Sheng Chen, Martin Erwig

Publication date 10 April 2014

Published in Proceedings of the 41st ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages (Search for Journal in Brave)

Full work available at URL https://doi.org/10.1145/2535838.2535863

zbMATH Keywords

type inferenceerror localizationchange suggestionschoice typestype error messagestype-error debugging

Mathematics Subject Classification ID

Theory of compilers and interpreters (68N20) Mathematical aspects of software engineering (specification, verification, metrics, requirements, etc.) (68N30) Specification and verification (program logics, model checking, etc.) (68Q60) Functional programming and lambda calculus (68N18)

Recommendations

• Systematic identification and communication of type errors
• Guided Type Debugging
• Compositional explanation of types and algorithmic debugging of type errors
• Dynamic witnesses for static type errors (or, ill-typed programs usually go wrong)
• A common framework using expected types for several type debugging approaches

Cited in

(10)

• Correcting type errors in the Curry system
• Guided Type Debugging
• Type error slicing in implicitly typed higher-order languages
• An error-tolerant type system for variational lambda calculus
• A common framework using expected types for several type debugging approaches
• Improving type error reporting for type classes
• Migrating gradual types
• Dynamic witnesses for static type errors (or, ill-typed programs usually go wrong)
• Compositional explanation of types and algorithmic debugging of type errors
• Systematic identification and communication of type errors

This page was built for publication: Counter-factual typing for debugging type errors

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q5408451)