HTTP/2 200 x-amz-id-2: kt6aoMgihdCbBs0nUNcJIOR4FS4xYoufrOOQDY/5sZQozoLbpN2mnt7XPoNwFA8GyWXFlZhcilKzdlDjnCPwlMDL8b5eBdTX x-amz-request-id: WCNDXBRYDQ4P19GK last-modified: Fri, 02 Dec 2022 04:06:10 GMT etag: "88be50cbd47bfccbccca32f6e4b38a77" server: AmazonS3 content-encoding: gzip via: 1.1 varnish, 1.1 varnish content-type: text/plain; charset=utf-8 accept-ranges: bytes date: Mon, 21 Jul 2025 22:28:25 GMT age: 0 x-served-by: cache-tyo11982-TYO, cache-maa10222-MAA x-cache: MISS, MISS x-cache-hits: 0, 0 x-timer: S1753136905.218732,VS0,VE447 vary: Accept-Encoding content-length: 381 From: Eric Wong Date: 2015-11-18T01:56:29+00:00 Subject: [ruby-core:71538] can we change SSLSocket#sysread_nonblock/syswrite_nonblock? They're private methods, but there's also RDoc for them so maybe people rely on them somewhere... I would like to do something similar to the commits done so far with https://bugs.ruby-lang.org/issues/11339 to remove kwarg parsing via C for performance. If we preserve the existing private methods, there'll be another layer of wrapper methods which I want avoid having.