The specific API chosen, however, used RAII guards to "guarantee" that the parent thread joined on the child thread within a certain scope. Unfortunately, it's possible to subvert the RAII guard by placing it within a ref-counted cycle, which results in its destructor never being run.
For the moment, the API is being moved back to "unstable" status.
We are considering a variety of ways to address the problem, including:
* Avoiding RAII guards in the API, instead using explicit closures to guarantee that the threads join.
* Introducing a way of marking types as "unsafe to leak", thereby allowing us to continue using the RAII-style API, but preventing use of the guard within reference counted pointers (which can leak).