2006
DOI: 10.1017/s0956796806006125
|View full text |Cite
|
Sign up to set email alerts
|

Featherweight generic confinement

Abstract: Existing approaches to object encapsulation either rely on ad hoc syntactic restrictions or require the use of specialised type systems. Syntactic restrictions are difficult to scale and to prove correct, while specialised type systems require extensive changes to programming languages. We demonstrate that confinement can be enforced cheaply in Featherweight Generic Java, with no essential change to the underlying language or type system. This result demonstrates that polymorphic type parameters can simultaneo… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
25
0

Year Published

2006
2006
2010
2010

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 20 publications
(25 citation statements)
references
References 28 publications
0
25
0
Order By: Relevance
“…In recent work, Noble et al [PNCB03,PNCR04] combined ownership and type parameterization by introducing generic ownership. This proposal reduces the annotation overhead for generic classes, but does not address the other shortcomings of ownership types.…”
Section: Related Workmentioning
confidence: 99%
“…In recent work, Noble et al [PNCB03,PNCR04] combined ownership and type parameterization by introducing generic ownership. This proposal reduces the annotation overhead for generic classes, but does not address the other shortcomings of ownership types.…”
Section: Related Workmentioning
confidence: 99%
“…A promising alternative approach is to combine ownership and generic types, as is being proposed by Potanin et al [16]. This is an area that we will be watching closely.…”
Section: Generic Ownershipmentioning
confidence: 99%
“…In contrast, the explicit approach, pioneered by Ownership Types [13], explicitly annotates types with extra information denoting objects' ownership: these annotations impose a significant syntactic burden on the programmer. While the earliest Ownership Types proposals supported nested objects as the unit of encapsulation ("deep ownership" [12,10]), more recent work has supported individual un-nested objects ("shallow ownership" [1,6]) and also per-package ownership [38,30]. Cyclone [19] is a type-safe language derived from C and it supports region-based memory management.…”
Section: Related Workmentioning
confidence: 99%