External Uniqueness Is Unique Enough

Clarke, Dave; Wrigstad, Tobias

doi:10.1007/978-3-540-45070-2_9

Cited by 113 publications

(127 citation statements)

References 34 publications

Supporting

Mentioning

127

Contrasting

Order By: Relevance

“…Owner-polymorphic methods take owners as parameters, similar to type parameters, and allow code to be reused with different owners [7,8,12,18]. The scope of owner parameters is limited to the current method, and an argument with owner parameters in its type cannot be statically aliased by the receiver (see Wrigstad's dissertation [21] for an extended discussion of this topic, in particular the "hide owner" pattern that lifts this restriction in certain situations).…”

Section: Owner-polymorphic Methodsmentioning

confidence: 99%

“…The scope of owner parameters is limited to the current method, and an argument with owner parameters in its type cannot be statically aliased by the receiver (see Wrigstad's dissertation [21] for an extended discussion of this topic, in particular the "hide owner" pattern that lifts this restriction in certain situations). As an illustration, an owner-polymorphic method in the Joline system [12,21] looks like this:…”

Section: Owner-polymorphic Methodsmentioning

confidence: 99%

“…Various forms of ownership types have also been used to enforce architectural restrictions [2], to avoid deadlocks and data-races [5], and for reasoning about disjointness of effects and absence of aliasing [9]. Ownership types have also been combined with uniqueness to enable uniquely referenced aggregates [4,3,12] and to overcome a problem with abstraction introduced by unique pointers in an object-oriented setting [12,21].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Existential Owners for Ownership Types.

Wrigstad¹,

Clarke²

2007

JOT

Self Cite

View full text Add to dashboard Cite

This paper describes a lightweight approach to adding run-time checked downcasts to a language in the presence of ownership types without the need for a run-time representation of owners. Previous systems [6] have required owners of objects to be tracked and matched at run-time which is costly in terms of memory and performance. Our proposal avoids run-time overhead to deal with owners and also extends the expressiveness of ownership-based systems enough to handle the Java equals idiom for structural equality comparison. The price is that it is sometimes impossible to downcast a type into a type that can be statically aliased. Our proposal is completely orthogonal and combinable with previous work.

show abstract

Section: Owner-polymorphic Methodsmentioning

confidence: 99%

Section: Owner-polymorphic Methodsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Existential Owners for Ownership Types.

Wrigstad¹,

Clarke²

2007

JOT

Self Cite

View full text Add to dashboard Cite

show abstract

“…construct [28] (or the equivalent Clean construct #!) and observer types [23] both fall into this category, and this approach has also been adopted by some non-functional languages where it is sometimes called borrowing [8]. It is, however, non-trivial to extend this approach to a concurrent setting with a partial order over execution steps; our approach can be regarded as one preliminary attempt to do so.…”

Section: Related Workmentioning

confidence: 99%

Uniqueness typing for resource management in message-passing concurrency

DeVries

Francalanza

Hennessy

2012

Journal of Logic and Computation

View full text Add to dashboard Cite

We view channels as the main form of resources in a message-passing programming paradigm. These channels need to be carefully managed in settings where resources are scarce. To study this problem, we extend the pi-calculus with primitives for channel allocation and deallocation and allow channels to be reused to communicate values of different types. Inevitably, the added expressiveness increases the possibilities for runtime errors. We define a substructural type system, which combines uniqueness typing and affine typing to reject these ill-behaved programs.

show abstract

“…Ownership types usually cannot easily handle change of owner, except for externally unique objects, i.e., for objects for which references from the outside are unique [17].…”

Section: Types For Hierarchic Shapesmentioning

confidence: 99%

Types for Hierarchic Shapes

Drossopoulou

Clarke

Noble

2006

Programming Languages and Systems

Self Cite

View full text Add to dashboard Cite

Abstract. Heap entities tend to contain complex references to each other. To manage this complexity, types which express shapes and hierarchies have been suggested. We survey type systems which describe such hierarchic shapes, how these types are used for reasoning about programs, and applications in concurrent programming.Most imperative programs create and manipulate heap entities (objects, or records) which contain references to each other forming intricate topologies. This creates complexity, and makes programs difficult to understand and manipulate. Programmers, on the other hand, tend to think in terms of shapes, categorizations and hierarchies.Thus, in the last decade, types describing shapes and hierarchies have been proposed to express programming intuitions, to support verification, and for synchronization and optimizations. We will discuss types for hierarchic shapes in terms of object oriented programming, because, even though the ideas are applicable to any imperative language, most of the related research was conducted in the context of object oriented languages.

show abstract

External Uniqueness Is Unique Enough

Cited by 113 publications

References 34 publications

Existential Owners for Ownership Types.

Existential Owners for Ownership Types.

Uniqueness typing for resource management in message-passing concurrency

Types for Hierarchic Shapes

Contact Info

Product

Resources

About