Rust has many container-like objects that may or may contain a value, like Box. Most of these have an unwrap() method that either obtains the inner value or panics the whole application.
Box is a bad example; it always has a value and can’t be unwrapped. It’s Result<T> and Option<T> that are the primary wrappers.
Result is for Errors, and Option is for nullables. If you consider it that way, the “issues” with unwrap are identical to other languages when errors and nulls aren’t properly handled.
Thank you for the easier captchas, and pre-emptively damn you for whatever evil thing CloudFlare will eventually do with their MITM access to everything.
can you explain the joke, i work at cloudflare
Rust has many container-like objects that may or may contain a value, like Box. Most of these have an unwrap() method that either obtains the inner value or panics the whole application.
Box is a bad example; it always has a value and can’t be unwrapped. It’s Result<T> and Option<T> that are the primary wrappers.
Result is for Errors, and Option is for nullables. If you consider it that way, the “issues” with unwrap are identical to other languages when errors and nulls aren’t properly handled.
I reckon the person you’re replying to knows exactly what unwrap is, because the last big famous Cloudflare outage was caused by it. They were making a joke of their own
Whoosh
sounds like an error handling issue
Yes it is. Typically you’d do some pattern matching to handle every possible case, but Unwrap is often used as a shortcut.
I shouldn’t worry about it.
Thank you for the easier captchas, and pre-emptively damn you for whatever evil thing CloudFlare will eventually do with their MITM access to everything.