@Mara i would really like compiler support for determining panic-free code regions with analogy to unsafe

@Mara how аbout using а much stable language like c++ instead of rust

@Mara
But wouldn't that make the API inconsistent? Since the other or*() methods don't change the type.

I guess there are quite a few Rust methods with innocent sounding names that can panic. clamp() is one I'm always wary of. There's also the ones that allocate memory, like for Vec and String.

#RustLang

@Mara yes please! 💯

I had a design where the || and && operators were overloadable, and there, res.unwrap() turned into

res || panic!()

and res.unwrap_or(default_value) into

res || default_value

and res.unwrap_or_else(callback) into

res || callback()

But if you're not doing that, renaming the methods would be great.

@Mara
Doesn't help that I'm associating unwrapping with unwrapping presents, and occasionally expecting what's inside. Like a perpetual birthday party.

(That the name "or_panic" would have been better isn't much of a hot take, but adding "or_panic()" now and deprecating "unwrap()" would likely be controversial.)