From: Eric Wong <normalperson@...>
Date: 2018-04-21T18:05:44+00:00
Subject: [ruby-core:86645] Re: [Ruby trunk Bug#14681] `syswrite': stream closed in another thread (IOError)

samuel@oriontransfer.org wrote:
> I reviewed your suggestion, and while it (in theory) works
> with the original example, it won't work with my actual use
> case which uses are set of shared threads to implement
> background workers - there is no join except when the thread
> pool is stopped.

If its threads background workers, perhaps SizedQueue is
better (and probably faster since 2.5).

Or, why bother closing the output early?

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>