Practical pluggable types for java

Papi, Matthew M.; Ali, Mahmood; Correa, Telmo Luis; Perkins, Jeff; Ernst, M.

doi:10.1145/1390630.1390656

Cited by 141 publications

(87 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our inference tool is built on top of the Checker Framework [21,6]. The tool extends the Checker Framework to specify type system constraints and preference ranking over qualifiers; it generates the constraints for the type systems by traversing the AST and it implements the set-based constraint solver described in Sect.…”

Section: Methodsmentioning

confidence: 99%

Inference and Checking of Object Ownership

Huang

Dietl

Milanova

et al. 2012

ECOOP 2012 – Object-Oriented Programming

Self Cite

View full text Add to dashboard Cite

Abstract. Ownership type systems describe a heap topology and enforce an encapsulation discipline; they aid in various program correctness and understanding tasks. However, the annotation overhead of ownership type systems has hindered their widespread use. We present a unified framework for specification, type inference and type checking of ownership type systems, and instantiate the framework for two such systems: Universe Types and Ownership Types. We present an objective metric defining a "best typing" for these type systems, and develop an inference approach that maximizes the metric. The programmer can influence the inference by adding partial annotations to the program. We implemented the approach on top of the Checker Framework and present the results of an experimental evaluation.

show abstract

Section: Methodsmentioning

confidence: 99%

Inference and Checking of Object Ownership

Huang

Dietl

Milanova

et al. 2012

ECOOP 2012 – Object-Oriented Programming

Self Cite

View full text Add to dashboard Cite

show abstract

“…Birka built a type-checker for an earlier dialect of Javari that lacked support for Java generics, and wrote 160,000 lines of code in Javari [6]. Correa later wrote a complete Javari implementation using the Checker Framework [20] and did case studies involving 13,000 lines of Javari [19]. The JQual inference system [14] (discussed above) can be treated as a type checker.…”

Section: Related Workmentioning

confidence: 99%

Inference of Reference Immutability

Quinonez¹,

Tschantz²,

Ernst³

ECOOP 2008 – Object-Oriented Programming

Self Cite

View full text Add to dashboard Cite

Abstract. Javari is an extension of Java that supports reference immutability constraints. Programmers write readonly type qualifiers and other constraints, and the Javari typechecker detects mutation errors (incorrect side effects) or verifies their absence. While case studies have demonstrated the practicality and value of Javari, a barrier to usability remains. A Javari program will not typecheck unless all the references in the APIs of libraries it uses are annotated with Javari type qualifiers. Manually converting existing Java libraries to Javari is tedious and error-prone. We present an algorithm for inferring reference immutability in Javari. The flow-insensitive and context-sensitive algorithm is sound and produces a set of qualifiers that typecheck in Javari. The algorithm is precise in that it infers the most readonly qualifiers possible; adding any additional readonly qualifiers will cause the program to not typecheck. We have implemented the algorithm in a tool, Javarifier, that infers the Javari type qualifiers over a set of class files. Javarifier automatically converts Java libraries to Javari. Additionally, Javarifier eases the task of converting legacy programs to Javari by inferring the mutability of every reference in a program. In case studies, Javarifier correctly inferred mutability over Java programs of up to 110 KLOC.

show abstract

“…Specifically, we did not modify the implementation or underlying Java type signature of any library. We implemented our qualifier and effect system on top of the Checker Framework [5,6], which is a framework for implementing Java 8 type annotation processors, providing support for, among other things, AST and type manipulation, and specifying library annotations separately from compiled libraries themselves. The Java UI syntax is expressed via Java 8's type annotations.…”

Section: Lemma 4 (Machine Preservationmentioning

confidence: 99%

“…Java UI provides three type qualifiers [5,6,7], each corresponding to instantiating an effect-polymorphic type with a specific effect:…”

Section: Effect-polymorphic Typesmentioning

confidence: 99%

See 1 more Smart Citation

Java UI : Effects for Controlling UI Object Access

Gordon

Dietl

Ernst

et al. 2013

ECOOP 2013 – Object-Oriented Programming

Self Cite

View full text Add to dashboard Cite

Abstract. Most graphical user interface (GUI) libraries forbid accessing UI elements from threads other than the UI event loop thread. Violating this requirement leads to a program crash or an inconsistent UI. Unfortunately, such errors are all too common in GUI programs. We present a polymorphic type and effect system that prevents non-UI threads from accessing UI objects or invoking UI-thread-only methods. The type system still permits non-UI threads to hold and pass references to UI objects. We implemented this type system for Java and annotated 8 Java programs (over 140KLOC) for the type system, including several of the most popular Eclipse plugins. We confirmed bugs found by unsound prior work, found an additional bug and code smells, and demonstrated that the annotation burden is low. We also describe code patterns our effect system handles less gracefully or not at all, which we believe offers lessons for those applying other effect systems to existing code.

show abstract

Practical pluggable types for java

Cited by 141 publications

References 33 publications

Inference and Checking of Object Ownership

Inference and Checking of Object Ownership

Inference of Reference Immutability

Java UI : Effects for Controlling UI Object Access

Contact Info

Product

Resources

About