iopipe v0.2.0 - safe update

[JN]

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).
>
> In this update, I've made it so nearly all of iopipe can be 
> used in @safe code. The one exception is the RingBuffer, which 
> can leave dangling pointers, hence the unsafety.
>
> 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.
>
> -Steve
>
> https://code.dlang.org/packages/iopipe

What's iopipe and what does it do? How does it compare with 
std.process?