TypeDevil: Dynamic Type Inconsistency Analysis for JavaScript

Dynamic languages, such as JavaScript, give programmers the freedom to ignore types, and enable them to write concise code in short time. Despite this freedom, many programs follow implicit type rules, for example, that a function has a particular signature or that a property has a particular type....

Celý popis

Uloženo v:
Podrobná bibliografie
Vydáno v:2015 IEEE/ACM 37th IEEE International Conference on Software Engineering Ročník 1; s. 314 - 324
Hlavní autoři: Pradel, Michael, Schuh, Parker, Sen, Koushik
Médium: Konferenční příspěvek
Jazyk:angličtina
Vydáno: IEEE 01.05.2015
Témata:
Arrays
Benchmark testing
Computer crashes
dynamic analysis
Dynamic languages
Instruments
JavaScript
Performance analysis
program analysis
Receivers
Runtime
types
ISSN:0270-5257
On-line přístup:Získat plný text
Tagy: Přidat tag
Žádné tagy, Buďte první, kdo vytvoří štítek k tomuto záznamu!
Popis
Shrnutí:Dynamic languages, such as JavaScript, give programmers the freedom to ignore types, and enable them to write concise code in short time. Despite this freedom, many programs follow implicit type rules, for example, that a function has a particular signature or that a property has a particular type. Violations of such implicit type rules often correlate with problems in the program. This paper presents Type Devil, a mostly dynamic analysis that warns developers about inconsistent types. The key idea is to assign a set of observed types to each variable, property, and function, to merge types based in their structure, and to warn developers about variables, properties, and functions that have inconsistent types. To deal with the pervasiveness of polymorphic behavior in real-world JavaScript programs, we present a set of techniques to remove spurious warnings and to merge related warnings. Applying Type Devil to widely used benchmark suites and real-world web applications reveals 15 problematic type inconsistencies, including correctness problems, performance problems, and dangerous coding practices.
ISSN:0270-5257
DOI:10.1109/ICSE.2015.51