From @carbin

For me, at least

my $s = IO​::Socket​::INET.new; $s.open('127.0.0.1', 80); $s.send('foo'); say "Lorem ipsum"; # I have Apache running on port 80 so this will work
Lorem ipsum

carlin@​cerberus​:~$ perl6

my $s = IO​::Socket​::INET.new; $s.open('127.0.0.1', 42); $s.send('foo'); say "Lorem ipsum"; # Nothing on port 42
carlin@​cerberus​:~$

GDB says​:

my $s = IO​::Socket​::INET.new; $s.open('127.0.0.1', 42); $s.send('foo'); say "Lorem ipsum"; # Nothing on port 42

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7f3272aad700 (LWP 6231)]
0x00007f3271c66465 in send () from /lib/libpthread.so.0

--
Carlin

From mestre.smash@gmail.com

Currently the IO​::Socket​::INET module is failing if can't create a
socket. In the meantime you have to 'use fatal;' in order to actually
see the message but that will change when void context detection is
implemented.

http://github.com/rakudo/rakudo/commit/5fc925ce246733a074a47c06bddd9c0d9effde0f

--
./smash

The RT System itself - Status changed from 'new' to 'open'

From @bbkr

On 2012.10 its

$ perl6 -e 'my $s = IO​::Socket​::INET.new; $s.open("127.0.0.1", 42); $s.send("foo"); say "Lorem
ipsum";'
Nothing given for new socket to connect or bind to
  in method <anon> at src/gen/CORE.setting​:9956
  in at src/gen/Metamodel.pm​:2401
  in any find_method_fallback at src/gen/Metamodel.pm​:2389
  in any find_method at src/gen/Metamodel.pm​:925
  in block at -e​:1

From @bbkr

So now error is misleading because it's not true that "nothing was given to bind to", it was failed
binding.

From @FROGGS

Are you sure it should work with positionals passed to .open instead of
named args passed to .new?

perl6 -e 'my $s = IO​::Socket​::INET.new(host => "127.0.0.1", port => 42);
$s.send("foo"); say "Lorem ipsum";'
Gives me​: connect failed​: Connection refused

From @carbin

Are you sure it should work with positionals passed to .open instead of named args passed to .new?

perl6 -e 'my $s = IO​::Socket​::INET.new(host => "127.0.0.1", port => 42); $s.send("foo"); say "Lorem ipsum";'
Gives me​: connect failed​: Connection refused

I believe the API for IO​::Socket​::INET has changed since this bug was originally filed (back in 2009!), so yes, the current behaviour looks correct.

@FROGGS - Status changed from 'open' to 'resolved'