Technically, `cork_ring_buffer_init` can fail, so in theory you should use `rpi_check` to test for that failure and propagate the error condition yourself.

That said, we no longer consider memory allocation failures to be errors — instead we abort the entire process for that.  So I'd actually suggest updating `cork_ring_buffer_init` to use `cork_calloc` instead of `calloc`, and then make it not check the result.  (`cork_calloc` will abort the process if the result is `NULL`, so there's no need to check ourselves after the call returns.)

Then you can update the documentation to remove the bits about returning error conditions, since that wouldn't be true anymore.