Toward general diagnosis of static errors
From MaRDI portal
Recommendations
Cited in
(18)- Improving type error reporting for type classes
- Finding fix locations for CFL-reachability analyses via minimum cuts
- Severity levels of inconsistent code
- Orion: High-Precision Methods for Static Error Analysis of C and C++ Programs
- Automatic Binding-Related Error Diagnosis in Logic Programs
- scientific article; zbMATH DE number 43241 (Why is no real title available?)
- scientific article; zbMATH DE number 1956467 (Why is no real title available?)
- scientific article; zbMATH DE number 1956560 (Why is no real title available?)
- scientific article; zbMATH DE number 1974023 (Why is no real title available?)
- Systematic identification and communication of type errors
- Error invariants
- scientific article; zbMATH DE number 1863891 (Why is no real title available?)
- scientific article; zbMATH DE number 2090852 (Why is no real title available?)
- scientific article; zbMATH DE number 1400020 (Why is no real title available?)
- Skalpel: a constraint-based type error slicer for standard ML
- Skalpel: a type error slicer for standard ML
- Static checker of semantic run-time errors
- Doomed program points
This page was built for publication: Toward general diagnosis of static errors
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q5408450)