meta: breaking API changes

[carllerche]

Tracks smaller breaking API changes that are left to make

io

• Copy should be private. (io: make Seek and Copy private #2935)
• Seek should be private. (io: make Seek and Copy private #2935)
• ReadBuf changes io: remaining AsyncRead / ReadBuf items #2769.

net

• TcpStream::poll_peek(&mut self, ...) -> &self. (net: switch socket methods to &self #2934)
• TcpStream::peek(&self) -> &self. (net: switch socket methods to &self #2934)
• UnixDatagram::try_send(&mut self, ...) -> &self. (net: switch socket methods to &self #2934)
• UnixDatagram::try_send_to(&mut self, ...) -> &self. (net: switch socket methods to &self #2934)
• UnixDatagram::try_recv(&mut self) -> &self. (net: switch socket methods to &self #2934)
• UnixDatagram::try_recv_from(&mut self) -> &self. (net: switch socket methods to &self #2934)
• UnixListener::accept(&mut self, ...) -> &self. (net: switch socket methods to &self #2934)
• UnixListener::poll_accept(&mut self, ...) -> &self. (net: switch socket methods to &self #2934)
• UnixListener::incoming(...) -> remove for now (track TcpListener::incoming())`. (net: switch socket methods to &self #2934)
• Consider moving split fns off of net types into -util.
• Revisit UCred, at the very least make struct fields private. (net: make UCred fields private #2936)

sync

• Mutex::const_new() -> new(). This may have to be conditionally const w/ parking_lot feature.
• Consider moving Mutex::lock_owned() -> tokio-util.
• mpsc::Sender::closed(&mut self) -> &self. (sync: change chan closed(&mut self) to closed(&self) #2939)
• mpsc::UnboundedSender::closed(&mut self) -> &self. (sync: change chan closed(&mut self) to closed(&self) #2939)
• broadcast move error types into broadcast::error module. (sync: move broadcast error types into broadcast::error module #2937)

time

• time::Delay -> time::Sleep. (time: rename Delay future to Sleep #2932)
• Move error types into time::error. (time: move error types into time::error #2938)

[akhilles]

Can #2928 be added to the list?

[carllerche]

@akhilles I think you made a typo w/ your issue ref (you refed the current issue). If you have a proposal for an API change for 1.0, create a new issue for it 👍

I don't think we are going to change any of the remaining APIs, so I will close this.