RFC: io and os reform

This RFC proposes a significant redesign of the `std::io` and `std::os` modules
in preparation for API stabilization. The specific problems addressed by the
redesign are given in the Problems section below, and the key ideas of the
design are given in Vision for IO.

[Rendered](https://github.com/aturon/rfcs/blob/io-os-reform/text/0000-io-os-reform.md)
I find it hard to see how this can be rationalized with the proposal to have hacky lossy abstractions (deadlines, cancellations) instead of using the native functionality. I don't think it's justified at all.