calling toString() on a connected UnixDomainSocket returns Socket[unconnected]

[inieves]

I noticed that UnixDomainServerSocket returns useful information on a call to toString(), but it's friend UnixDomainSocket does not return useful information, it actually returns incorrect information:
Socket[unconnected]

More useful and correct output would be the path that was used to create the socket.

I have not tested the Win32NamedPipeSocket but I suspect a similar issue would occur.

[eed3si9n]

I guess toString is coming from the Socket class? Here's a PR to try to fix this - #44