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 bitterly bad at robust software development in practice?
Autism.
>>108457559>why does the program potentially panic here?>oh it doesn't, the value is always valid>then why use a type that can express an invalid state?>oh it's because this is the most ergonomic way of tricking the borrow checkerEvery single time
>>108457559hahah
>>108457559I just use picrel
>>108457559piddle
>>108457559>>108450646>stale addition to the tard circulation by the ever-triggered anti-rust "grep researcher" IzzatBot.i guess it's hard to come up with better stuff when the (((help))) is busy. llm web search can only go so far
>>108457755>its not a vulnerability, it is useless bloatok?
Reminder that Rust is government promoted trash.Promoted by the same brainfucked idiots who are losing in Iran currently.
>>108458195I love how the jews pretend everything they don't like is promoted by them and even sometime do so lmao.Funnily enough there is no rust hate thread on shabbat or whenever Israel gets bombed.
>>108458195>there are no persian, chink, and russki rustacians
>108458267rust was literally dead for years, the fucking creators of rust got booted from Mozilla and their prestige project, Servo, was in a limbo, because nobody developed on it without payment.Until shekels from corrupt and dumb government child raping pedophiles came in, then suddenly we got this flood of promotions.None of you people existed before that.
>>108458508> None of you people existed before that.Almost everyone who liked Haskell, OCaml, Scala, etc, liked Rust way before it was popular.Those people like traits, path dependent types, disjoint union types, etc.Even if they agree borrow checker / ownership can be pain in the ass, there are no languages closer to C++ and at the same time supporting so many advanced FP type system features.
>>108458508>>108458556samefag
>>108458713You good buddy? Anyway, thread bump appreciated.
>>108458905faggot whore detected, please kys immediately
>>108457755>Use an unsafe block? Oh my heavens no!>Writes unsafe safe code
>>108458556>FP type system featuresyou're so dumb
>>108457755it's no different than de-referencing potentially nullable pointers in most other languages. the unwrap is just a form of assert in this case.
>>108458508Yep. Everyone can trivially see that for themselves too (picrel). It basically died in 2020, and only showed signs of life again years later. All thanks to president Trump.
>>108458195>>108458508what mental illness is this? this isn't on-topic /g/. this is just schizo bullshit.
>>108459215it's IzzatBots' "smart" attempt at misdirection and "no u"-ing lol
>>108457559Because safe rust is nearly impossible. It requires predictability, but useful software tries to model the real world, and that implies unpredictability and imperfection.
>>108459267Safe Rust is sometimes difficult because modeling complex real world relationships requires patterns (like shared mutable state or cyclic references) that don't map cleanly to Rust's ownership model.Fixed that for you.
>>108459087If you had even brushed, however lightly, against the currents of Homotopy discourse, you would feel at once how it resonates with the Curry-Howard correspondence, how it echoes through type families, ML functors, Scala’s path-dependent types, and ultimately gestures toward fully dependently typed languages as a kind of distant, almost inevitable horizon against which all these ideas are measured.
>>108459340whoa.
>>108459287can you provide examples where the problem itself (not implementations solving it) requires patterns like shared mutable state or cyclic references
>>108459087Newfag who didn't even read ATAPL detected. I bet you're one of those who thinks "functional programming is having lambda functions and map/reduce", ignoring the massive context of type systems research going for more than half century in FP sphere.
>>108457559Forcing you to unwrap is more robust than the alternative
>>108457755unwrap makes zero difference in terms of borrowing
>>108458556FP sucks
>>108458556So why is a bad thing that C++ doesn't support all those mental illnesses you call "features"?>>108458508Based AF.
>>108459215>>108458267>>108458713>>108458984^ glowie zogbots
>>108461851>>108458984
>>108461838C++ does support ALL of this and more, and people been using all of this unironically in C++ since early 2000s via boost fuckery first and using more stuff later and nowadays some of it is in C++ standard library, like type traits, etc. It's just less systemic and ergonomic in C++, it's implemented using mechanisms that were not designed for it initially, it can lead to hard complilation errors and long compile times, etc. In Rust all those features are relatively simple, ergonomic, well organized and well specified, and subject to regular improvements and optimizations.
>>108462534>C++ does support ALL of this and more>no directory handles for relative lookup though>despite Windows, Linux, and Mac all supporting them>meaning it's back to C bindings
>>108462607What does this comment have to do with type systems?
>>108462745>type systemsI thought we were talking about features *in general*? >>108458556
>>108457559Just vibecode bro
>>108462776I didn't touch my Rust app since summer, decided to give it a go today without vibecoding as an extra challenge. So I did bump language edition from 2021 to 2024, updated major dependencies and implemented drag-n-drop for reordering tabs. Messed around with ownership/borrowing issues when thing can be borrowed simultaneously immutably for the whole function and mutably in the scope of closure that goes into ui callback. Sorted it out by being slightly inefficient (finding index of element in array of tabs multiple times instead of once, because accessor method is called inplace so no extra binding that causes immutable borrow), but at least no Rc<RefCell<..>> trash. For the future, if the same problem arises in context where this actually matters for performance and arrays are big, I decided I'll try salvia signals+derived!, basically classic reactive programming where dependent cells update/recompute automatically when their dependencies change, and only when it's needed. Overall, a very good experience for not touching Rust for more than half a year, especially considering that I used vibecoding before on this codebase so the code I had to deal with wasn't even fully written myself in the first place.
>>108459287Are we talking shared mutable state protected by a synchronization primitive, or not? Because the first one is supported OOTB in safe rust
>saar, rust bad because the borrow checker wont let me write garbage code like my shitty cs50 fizz buzz implementation that uses pointersJust nuke India off the face of the planet already please.
>>108464590Indians use Rust as well, for instance in Google's Fuchsia.
