[ruby-core:110642] [Ruby master Feature#19064] UDPSocket#bind does not take AddrInfo, despite documentation saying it should

["jeremyevans0 (Jeremy Evans)" <noreply@ruby-lang.org>]

Issue #19064 has been updated by jeremyevans0 (Jeremy Evans).

Tracker changed from Bug to Feature
ruby -v deleted (ruby 3.2.0dev (2022-10-16T09:31:08Z master ba9c0d0b9f) [x86_64-linux)
Backport deleted (2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN)

`UDPSocket` is not a subclass of `Socket`, so the fact that `Addrinfo` instances work for `Socket` (as documented), but do not work for `UDPSocket` is not a bug.  I agree that having `UDPSocket` support `Addrinfo` would be useful, switching to feature request.

----------------------------------------
Feature #19064: UDPSocket#bind does not take AddrInfo, despite documentation saying it should
https://bugs.ruby-lang.org/issues/19064#change-99982

* Author: mcr (Michael Richardson)
* Status: Open
* Priority: Normal
----------------------------------------
https://docs.ruby-lang.org/en/master/Socket.html#method-i-bind says that this code should work:

``` ruby
require 'socket'

# use Addrinfo
socket = Socket.new(:INET, :STREAM, 0)
socket.bind(Addrinfo.tcp("127.0.0.1", 2222))
p socket.local_address #=> #<Addrinfo: 127.0.0.1:2222 TCP>
```

and it does, but UDPSocket does *not* like Addrinfo:

``` ruby
socket = UDPSocket.new(Socket::AF_INET6)
ai=Addrinfo.udp("127.0.0.1", 2224)
socket.bind(ai, 0)
````

A reason to use an Addrinfo rather than a string is because it came from, for instance, Socket.getifaddrs, and might have scope and other information attached, like:

``` ruby
#<Addrinfo: fe80::f58e:d5ea:41e0:2555%eth0>
```

Seen on versions back to 2.6.6, but tested with ruby-head to be sure.



-- 
https://bugs.ruby-lang.org/