ry is
exhausted.  In addition, any write error will cause a &rsquo;c-write-error
exception to be thrown out of this procedure.  With versions of this
library before 0.13, &rsquo;c-write-error exceptions arising after the first
write would propagate out of event-loop-run! and could not be caught
locally.  Having write exceptions (say, because of EPIPE) interfering
with anything using the event loop in this way was not a good
approach, so from version 0.13 of this library all write exceptions
will propagate i