.. there are some additional FIXME nags in net_tcp (L 1012) about blocking
because libuv is holding unsafe ptrs to task local data. the proposed
fix going is not really feasible w/ the current design, IMO, but i'll
leave it there in case someone really wants to make the case without
creating more hassle than it's worth.

.. stub out some brokeness in net::tcp as a result of ipv6 coming online

replaces net::ip's previously, hand-rolled impl for ipv4 addr parsing..
we're relying on libuv, now

i mistook an "unconstrained type" error, due to type-inference messup
because i didnt have return vals in some closure wired-up right, for being
due to not having a str as a str/& (a str will actually auto-coerce to a
str/&, so str::as_slice was erroneously added. my bad).

needs work. probably the slice code and/or the way that the tcp_socket_buf
is wrapped in a shared box

need to do some other work, in the subsequent commit, to add io::writer,
then tests.

* updated rustdoc info for several functions
* changed read_stop to take control of the port returned by read_start
* made write_future do an explicit data copy with the binary vector it is
passed

.. confounded resolve!

libstd: Work around some metadata infelicities that are causing problems in resolve3, and remove an unused glob

Conflicts:

	src/libstd/net_tcp.rs
	src/libstd/par.rs