Generic Types And Functions: Type Erasure
The ability to parameterize types via generics provides strong readability benefits for developers and users of your code. It also
provides the typechecker the necessary information to ensure that you are the code in the way it was intended. For example, having a
Box<int> as a parameter type to a function clearly shows the type that the
Box should contain and the typechecker can use this information as well.
However, with the exception of the return type for async functions
Awaitable<T>, support for generics is only at the typechecker level
via type annotations; they do not exist at runtime. Generic type parameters and arguments and stripped out (i.e., erased) before
execution. Using our Box example above, this means that
Box<int> really becomes
Box at runtime, and HHVM will allow you to pass
int Boxes to the function.
While having the generic parameterization is certainly a great benefit, there are some limitations you need to be aware of because of type erasure at runtime. A type parameter T cannot be used in the following situations:
- Creating instances using
- Casting (e.g.,
- In a class scope, e.g.,
- As the right-hand side of an
- As the type of a static property.
- As the type of the exception in a catch block (e.g.,
catch (T $exception)).
For a possible alternative to instantiation, class scope and
instanceof usage, Hack provides a construct called
Classname<T> that extends the PHP representation of