iopipe v0.2.0 - safe update

[Joseph Rushton Wakeling]

On Sunday, 28 June 2020 at 18:57:22 UTC, Steven Schveighoffer 
wrote:
> Just wanted to post that I finished my update of iopipe to be 
> @safe. I still have some work to do with std.io so things are 
> more usable (next on my list is to make standard handles 
> accessible).

Cool, and congratulations :-)

> Inside iopipe is a RefCounted type that is @safe. It uses the 
> GC for memory management, so while destruction is synchronous, 
> the memory itself is left to the GC to clean up.

One concern here -- this means that one cannot control when an 
app using this might block for GC, right?  Any thoughts on how a 
user could get more deterministic control on when the memory 
would be released?