zlacker

[parent] [thread] 4 comments
1. roland+(OP)[view] [source] 2025-12-05 18:31:51
As someone unfamiliar with Rust (yet! it's on my ever growing list of things I'd like to absorb into my brain), unwrap_or_else() sounds like part of the "What You See Is What I Threatened the Computer To Do" paradigm.
replies(2): >>Y_Y+X2 >>wongar+Nb
2. Y_Y+X2[view] [source] 2025-12-05 18:45:12
>>roland+(OP)
> INTERCAL has many other features designed to make it even more aesthetically unpleasing to the programmer: it uses statements such as "READ OUT", "IGNORE", "FORGET", and modifiers such as "PLEASE". This last keyword provides two reasons for the program's rejection by the compiler: if "PLEASE" does not appear often enough, the program is considered insufficiently polite, and the error message says this; if it appears too often, the program could be rejected as excessively polite.
replies(2): >>strbea+T6 >>roland+6T
◧◩
3. strbea+T6[view] [source] [discussion] 2025-12-05 19:00:16
>>Y_Y+X2
Immediately thought of INTERCAL :)
4. wongar+Nb[view] [source] 2025-12-05 19:21:08
>>roland+(OP)
There are also the equally threatening and useful `map_or_else` (on Result and Option) and `ok_or_else` (on Option and experimentally on bool)
◧◩
5. roland+6T[view] [source] [discussion] 2025-12-05 23:18:15
>>Y_Y+X2
Oh wow! That's amazing! "I came to learn Computer Science, but I left with good bedside manners".
[go to top]