TcpListener docs example contains an explicit drop that can never be reached

[sfackler]

The incoming iterator never returns None, so the drop at the end will never be reached. The explicit matching against the socket result also seems potentially nonconventional docs-wise?

https://doc.rust-lang.org/std/net/struct.TcpListener.html#examples

[abonander]

Also, what are the semantics of this iterator when the listener is set to nonblocking mode? If it's equivalent to accept() it should run the loop with WouldBlock errors until a connection is made.

[sfackler]

That's what it'd do, yeah. The next method is super simple: https://doc.rust-lang.org/src/std/up/src/libstd/sys/unix/ext/net.rs.html#532