[#82706] [Ruby trunk Bug#13851] getting "can't modify string; temporarily locked" on non-frozen instances — cardoso_tiago@...
Issue #13851 has been updated by chucke (Tiago Cardoso).
3 messages
2017/09/07
[#82853] [Ruby trunk Bug#13916] Race condition when sending a signal to a new fork — russell.davis@...
Issue #13916 has been reported by russelldavis (Russell Davis).
3 messages
2017/09/19
[#82892] [Ruby trunk Bug#13921] buffered read_nonblock doesn't work as expected using SSLSocket — cardoso_tiago@...
Issue #13921 has been updated by chucke (Tiago Cardoso).
3 messages
2017/09/20
[ruby-core:83014] Re: [Ruby trunk Feature#9323] IO#writev
From:
Eric Wong <normalperson@...>
Date:
2017-09-26 00:57:55 UTC
List:
ruby-core #83014
glass.saga@gmail.com wrote: > The main purpose of IO#writev is to make a chance for users to > write multiple buffers atomically, not to improve performance. IO#write on Array#join result is atomic, too; but Array#join can result in too large buffers and excessive memory use. I wrote benchmarks for shards io-extra project on Rubyforge years ago, but I guess that email is no longer available publically. I've quoted and reposted the test to spew: https://80x24.org/spew/20170926005509.GA22313@starla/raw Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>