From: akr@... Date: 2017-06-16T08:56:26+00:00 Subject: [ruby-core:81707] [Ruby trunk Bug#13407] We have recv_nonblock but not send_nonblock... can we add it? Issue #13407 has been updated by akr (Akira Tanaka). I cannot remember why I didn't add send_nonblock. However I feel adding send_nonblock is considerable because sendmsg is much complex that send/sendto. ---------------------------------------- Bug #13407: We have recv_nonblock but not send_nonblock... can we add it? https://bugs.ruby-lang.org/issues/13407#change-65403 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- We have recv_nonblock, read_nonblock, write_nonblock but not BasicSocket#send_nonblock. Is this a mistake? -- https://bugs.ruby-lang.org/ Unsubscribe: