schedule_read t ~on_eof ~on_read will setup on_read and on_eof as callbacks for when bytes are available in t for the application to consume, or when the input channel has been closed and no further bytes will be received by the application.

Once either of these callbacks have been called, they become inactive. The application is responsible for scheduling subsequent reads, either within the on_read callback or by some other mechanism.

close t closes t, indicating that any subsequent input received should be discarded.

is_closed t is true if close has been called on t and false otherwise. A closed t may still have bytes available for reading.