This is why #Rust is not only about memory safety/performance, but about correctness 馃憞
Did you know that in #JavaScript when `fetch`ing the same Request/Response twice will error (when containing a body)!?
It is because bodies are Streams, which can only be read once! You can clone the Request/Response/Body, but this comes with its own caveats (in the worst case the clone will buffer the body fully in memory!).
#RustLang solves this by borrow checking and good API design...
1/3
For example `reqwest` is a popular crate ("crate" means "library" in Rust) for doing requests.
When actually sending the request (via `send` method), `self` is consumed, which means the request object cannot be used afterwards:
https://docs.rs/reqwest/latest/reqwest/struct.RequestBuilder.html#method.send
Now you might think: Can't we just `clone` it like in JavaScript!?
Well..._maybe_ 馃槈
https://docs.rs/reqwest/latest/reqwest/struct.RequestBuilder.html#method.try_clone
It can only be cloned, if it is _not_ a Stream (unlike JS, bodies don't need to be Streams)!
2/3
This saves us from potentially reading the underlying stream twice, with the second either already being drained by the first stream or a potentially costly buffering in memory (like in JS)!
Thank you Rust! 鉂わ笍 
Some more links to the relevant JS articles (haven't fit in first toot):
Locked and disturbed streams:
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#locked_and_disturbed_streams
Response.clone()
https://developer.mozilla.org/en-US/docs/Web/API/Response/clone
3/3
