From: samuel@... Date: 2017-04-07T00:03:17+00:00 Subject: [ruby-core:80596] [Ruby trunk Bug#13407] We have recv_nonblock but not send_nonblock... can we add it? Issue #13407 has been updated by ioquatix (Samuel Williams). Thanks for the quick reply and interesting information. I think I'd like to see send_nonblock, but I'm not sure if it's implementation is different than sendmsg_nonblock. If it's not different, an alias may be sufficient. ---------------------------------------- Bug #13407: We have recv_nonblock but not send_nonblock... can we add it? https://bugs.ruby-lang.org/issues/13407#change-64096 * 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: