Abstract

We integrate existential types into a strongly typed C-like language. In particular, we show how a bad combination of existential types, mutation, and aliasing can cause a subtle violation of type safety. We explore two independent ways to strengthen the type system to restore safety. One restricts the mutation of existential packages. The other restricts the types of aliases of existential packages. We use our framework to explain why other languages with existential types are safe. 1

Citations

573	The Definition of Standard ML (Revised - Milner, Tofte, et al. - 1997
557	From system F to typed assembly language - Morrisett, Walker, et al. - 1999
347	Enforcing high-level protocols in low-level software - DeLine, Fähndrich - 2001
274	Cyclone: A safe dialect of C - Jim, Morrisett, et al. - 2002
267	G.D.: Abstract types have existential types - Mitchell, Plotkin - 1988
146	Typed closure conversion - Minamide, Morrisett, et al. - 1996
109	Comparing object encodings - Bruce, Cardelli, et al. - 1999
56	A simplified account of polymorphic references - Harper - 1994
27	Type Classes with Existential Types - Laufer - 1996
18	et. al.: Clu Reference Manual - Liskov - 1979
11	Towards an ML-style polymorphic type system for C - Smith, Volpano - 1996
1	Existential types for imperative languages: Technical results - Grossman - 2001