From: ko1@... Date: 2014-12-15T09:35:43+00:00 Subject: [ruby-core:66844] [ruby-trunk - Feature #10600] [PATCH] Queue#close Issue #10600 has been updated by Koichi Sasada. Interesting. I understand your motivation. I have several questions (design choise) (1) should we flush all remaining items in queue when it is closing? This specification can be interrupt. Now, your proposal does not flush. (2) should we allow "re-open"? We can make it. But it makes thread programming difficult to control. ---- Maybe we need to survey other language / libraries. ---------------------------------------- Feature #10600: [PATCH] Queue#close https://bugs.ruby-lang.org/issues/10600#change-50406 * Author: John Anderson * Status: Open * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- In a multiple-producer / multiple-consumer situation using blocking enq and deq, closing a queue cleanly is difficult. It's possible using a queue poison token, but unpleasant because either producers have to know how to match up number of poison tokens with number of consumers, or consumers have to keep putting the poison back into the queue which complicates testing for empty and not blocking on deq. This patch (from trunk at b2a128f) implements Queue#close which will close the queue to producers, leaving consumers to deq the remaining items. Once the queue is both closed and empty, consumers will not block. When an empty queue is closed, all consumers blocking on deq will be woken up and given nil. With Queue#close, clean queue shutdown is simple: ~~~ ruby queue = SizedQueue.new 1000 consumer_threads = lots_of.times.map do Thread.new do while item = queue.pop do_work item end end end source = somewhat_async_enumerator producer_threads = a_few.times.map do Thread.new do loop{queue << source.next} end end producer_threads.each &:join queue.close consumer_threads.each &:join ~~~ ---Files-------------------------------- queue-close.diff (5.18 KB) -- https://bugs.ruby-lang.org/