From: Eric Wong <normalperson@...>
Date: 2017-04-06T20:30:13+00:00
Subject: [ruby-core:80595] Re: [Ruby trunk Bug#13407] We have recv_nonblock but not send_nonblock... can we add it?

samuel@oriontransfer.org wrote:
> Bug #13407: We have recv_nonblock but not send_nonblock... can we add it?
> https://bugs.ruby-lang.org/issues/13407

> We have recv_nonblock, read_nonblock, write_nonblock but not BasicSocket#send_nonblock. Is this a mistake?

I've sometimes wondered that too...

However we have sendmsg_nonblock, is that insufficient?

So I also wonder why recv_nonblock exists, since
recvmsg_nonblock is a superset of its functionality;
and redundant methods waste memory...

It's too late to remove recv_nonblock, of course.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>