> Any update on newruntime status? It seems that the new GC is a bit of an
> admission of defeat on that front, or at least an admission that the new
> runtime won't be ready for use with async any time soon.
Well good question. Let me try to untangle it: We have 2 ("araqsgc" and
"newruntime") different, competing designs with much overlap in the
implementation, both use the destructor based strings and seqs, for example.
Both also focus on these goals (and more-or-less achieve them):
* Work well with any heap size.
* Work well with a shared heap.
* Work well with clang's sanitizers and valgrind.
Whatever will support `async` first will "win" and so far araqsgc looks like
it's winning, which means newruntime's importance will be downplayed to a new
`--gc:none` switch for embedded development. If that happens, `async` should
still support "newruntime", but it is not that important.
Ok, now what are the differences? How does "araqsgc" work? Will tell you later,
I have to go now.
