https://blog.cloudflare.com/18-november-2025-outage/>unwrap() breaks lots of websites worldwidehttps://grep.app/search?f.lang=Rust&q=unwrap%28%29>500K+ Rust files that contains unwrap()https://github.com/ruffle-rs/ruffle/blob/master/core/src/avm2/globals/date.rs>84 occurrences of unwrap() in one fileWhy are Rust programmers so bad at robust software development in practice?
>>108450646Narcissism. Mental illness.
They should arguably have called unwrap() for something like unwrap_or_else_panic(), and make it a compile-time error to call expect() with an empty string literal argument.
>>108450713why?
>>108450746>>108450646
>>108450797that isn't justification. use your own words.
>>108450816>>108450646
>>108450835I'll help you, since you're clearly retarded.how does making the method name longer change anything? why do you hold .unwrap() to a higher standard than assert!() when it's the same thing?should assert!() be renamed assert_or_panic!()? what about in C and C++, why is it ok to call _exit(int) which ostensibly does what unwrap() does, but worse? or abort()? how about uncaught exceptions? before you mention non-standard compiler flags, it's very likely the C++ std you're linking with was built with exceptions, whether you like it or not.you don't really have any argument though. you're just another moron.
>>108450646>so some code had a bug>EXIT_FAILURE caused major breakage>a lot of code has EXIT_FAILURE>https://grep.app/search?f.lang=C&q=EXIT_FAILURE>one file had a lot of EXIT_FAILURE>this is very bad[Live Tips] Learn This Simple Trick To Improve Your Code 42x Fold: move EXIT_FALURE to the two callees, and instances of EXIT_FAILURE will go from 84 to 2. Now grepper researchers will think your code is okay.Subscribe to my /g/eet weekly tips for similar code improvement tricks.
>>108450646reminder that claudflare outrage was caused by AI slop and dumbass dev not reviewing it.
>>108450861>>108450871Rust retards being triggered.Imagine being given good pattern matching and good tagged unions. And then resorting to lots and lots of usage of unwrap().Rust developers are a joke.
>>108450646In reality: most of them are using AI
>>108450914>still no argumentyou're very retarded.
>>108450946You are describing yourself, not me, triggered Rust retard.
do people still write rust by hand?
>>108451038ew fr we dont unc is all vibe n shi
>>108450914omg THIS THIS THISit's retarded to call unwrap() when you canlet val = match val { Ok(v) => v, Err(e) => panic!("got unexpected error {e:?}"),};
let val = match val { Ok(v) => v, Err(e) => panic!("got unexpected error {e:?}"),};
>>108452061not sure if retarded or baiting
>>108452061Have you considered bubbling up the error (for instance by using the usual operations like map() followed at some point by '?') or handling it, or at least use expect() with a proper error message (not "got unexpected error" you piece of shit trash-whore) and in-code documentation of what can go wrong?You know, utterly basic stuff?Fucking hell, your post reveals you to be an ultra-retarded Rust whore. How can proper error handling be so foreign to you?
>>108453216oh you mean like bubbling up the error back to the user to run it properly
>have to wrap your c# code in unsafe blocks to do anything worth doingreally activates the almonds
>>108453216omg THIS.some rust whores have context as a part of the error value itself, but this is retarded. writing expect()s is clearly superior.
>>108450646you are a retard if you think the issue was unwrap, some jeet made code that generated a broken config and you blame the software that refused to use an invalid config instead of the jeet responsible for it, the fact that it wasn't tested to be valid before being deployed and the fact that the monitoring / orchestration system didn't rollback the deploy when it was obviously falling.You are a retard that understand nothing about software and shouldn't be on /g/
>>108450713Every rust dev knowns what unwrap does, you just proved to be a nocoder.And exiting with an error was the desired behavior in that case. See : >>108453890
>>108453683>>108453695>>108453890>>108453905Rust whores being utterly triggered.
>>108450646Eventually they will figure out that all C "issues" are just "ideal =/= real" issues, and some schizos will start the loop again by making yet another safer programming language by saying Rust is outdated and new thing is current thing
>>108453927Yeah, that's what really keeps me up at night, something even better than rust at safety coming into existence.
