The case for deadlines
Rust aims to be the foundation of fast and robust software. A thorn in that side is the choice of timeout-centric APIs for I/O and multithreading. I posit this was a bad choice and it needs to be remedied as soon as possible before more APIs proliferate this (possibly accidental) design decision.
Motivating example: time limited network client request
Task: connect to a remote server, send a request, receive response with an end-to-end timeout of 10 seconds.