Introducing custom core-type abstracts is rarely necessary in user code as it requires the Haxe
target to be able to make sense of it. However, there could be interesting use-cases for authors of
macros and new Haxe targets.
In contrast to opaque abstracts, core-type abstracts have the following properties:
- They have no underlying type.
- They are considered nullable unless they are annotated with:notNullmetadata.
- They are allowed to declare array access (2.8.3) functions without expressions.
- Operator overloading fields (2.8.2) that have no expression are not forced to adhere to the
Haxe type semantics.
2.9 Monomorph
A monomorph is a type which may, through unification (3.5), morph into a different type later.
We shall see details about this type when talking about type inference (3.6).