Resolve "Make socket accessible from a Pipe"

Closes #15 (closed)

I don't see much use for it and the existence of "random" i32 identifiers for types seems weird. The only way to get a Pipe is through messages coming from a socket or through the socket's pipe event callback, so it seems like the user will always be able to tell where the pipes came from.

Removing the ID functions also makes sense. It will help hide the C aspect of the underlying library and all of my imagined use-cases for it have been solved via implementing bunches of common traits.