Companion

Declarations related to exception objects.

Create a mutable object type using the provided ObjectLayoutVariant, but without initializing its fields. The caller is responsible for initializing the fields before use.

Extract the field type at the specified slot index.

Answer the set of named base types for the specified user-defined object type.

Answer information about the user-assigned name of the specified user-defined object type.

Answer the user-assigned names of the specified user-defined object type.

Create an object type using the given A_Map from A_Atoms to types.

Create an object type from the specified A_Tuple.

Remove a type name from the specified user-defined object type. If the object type does not currently have the specified type name, or if this name has already been removed, do nothing.

Assign a name to the specified object type. If the only field key A_Atoms in the object type are special atoms, then the name will not be recorded (unless allowSpecialAtomsToHoldName is true, which is really only for naming special object types like Exceptions.exceptionType). Note that it is technically legal for there to be multiple names for a particular object type, although this is of questionable value.

Produce the given object type's ObjectLayoutVariant's variantId.

Answer the metatype for all object types. This is just an instance meta on the mostGeneralObjectType.

Answer the top (i.e., most general) object type.

A canonical mapping of all object types that have become shared. Without too much runtime cost, this should reduce the memory footprint, as well as improve the efficiency of the VettingsCache, stored inside each ObjectDescriptor that has been compared against a shared object type.

The CheckedMethod for staticTypeTagOrdinal.