The AssemblyScript Runtime
The runtime provides the functionality necessary to dynamically allocate and deallocate memory of objects, arrays and buffers, as well as keep track of references that are no longer used.
Dynamically allocates a chunk of memory of at least the specified size and returns its address. Alignment is guaranteed to be 16 bytes to fit up to v128 values naturally.
Dynamically changes the size of a chunk of memory, possibly moving it to a new address.
Frees a dynamically allocated chunk of memory by its address.
Retains a reference to an object. The object doesn't become collected as long as there's at least one retained reference. Returns the retained reference.
Releases a reference to an object. The object is considered for collection once all references to it have been released.
Forces a full garbage collection cycle. By default this means that reference cycles are resolved and possibly collected.
Concrete visitor implementation called during traversal. Cookie can be used to indicate one of multiple operations.
Obtains the runtime type information for objects with the specified runtime id. Runtime type information is a set of flags indicating whether a reference type is managed, an array or similar, and what the relevant alignments when creating an instance externally are etc.
__visiton each global that is of a reference type. Not used anymore (originally provided to support tracing GCs) but still here for possible future use.
__visiton each member of the object pointed to by
Obtains the unique internal class id of a reference type.
The full runtime is based on the TLSF memory manager and a pure reference counting garbage collector and provides all the functionality necessary. The half alias is essentially the same, but doesn't expose the runtime API so unused runtime code can be DCE'ed.
The stub runtime, though fully functional, provides minimal dynamic memory allocation but no deallocation. Useful for prototyping or very short-lived programs with hardly any memory footprint. The none alias is the same, but doesn't expose the runtime API so unused runtime code can be DCE'ed.
The underlying reference counting implementation works very similar to other implementations. When an object is stored in a local, global or field, its reference becomes retained (reference count is incremented by 1), respectively when it becomes deleted, it is released (reference count is decremented by 1). Once the reference count reaches zero, the object is considered for collection and the reference count of all contained objects (fields, array elements etc.) is decremented by 1. Now, if an object is inherently acyclic (most objects are), it is free'd right away, while otherwise it is added to a cycle pool and considered for cycle collection on the next
Differences to other implementations include:
- A new object from
__allocdoesn't start with a reference count of 1, but 0.
- When an object is returned from a function, it remains at RC + 1 and the caller is expected to release it.
- Functions with reference type arguments retain each such argument when called, and release it again when exited. This can't be counted on, however, because the compiler may decide to eliminate these where unnecessary.
- Getters, setters, operator overloads and constructors are function calls and behave like one.
Even though the rules are simple, working with the runtime internals within standard library code can be tricky and requires knowledge of where the compiler will insert runtime calls automatically. For instance
changetypeing a pointer to a reference type or vice-versa has no side-effects. For example in a
changetype<Ref>(ptr)the pointer is untracked before, and the reference becomes tracked afterwards, but there's nothing inserted in between.
storeand similar built-ins aren't functions but intrinsics and as such have no side-effects. For example a
load<Ref>(...)is equivalent to a
store<Ref>(..., ref)equivalent to a
GOOD: In case of doubt, the following pattern is universal:
var ref = changetype<Ref>(__alloc(SIZE, idof<Ref>())); // assignment retains, RC=1 // ... safe ... return ref; // knows `ref` is already retained and simply returns it
BAD: A pattern one shouldn't use is:
var ptr = __alloc(SIZE, idof<Ref>()); // RC=0 // ... not safe while RC=0 ... e.g.: someFunc(changetype<Ref>(ptr)); // might, or might not, free the object!
BONUS: Beware of runtime calls in conditional expressions like a ternary IF, logical AND or OR. Each arm can be in either of two states: Either in-flight if immediately retained/returned or not if the expression or the target doesn't support it. Don't fight the compiler there.