â„–21409[Quote]
both sides are right.
in other functional languages unwrap usually refers to accessing the inner value of an object, so that might have caused some confusion. also methods like unwrap_or or unwrap_or_default exist that dont panic on Option::None
on the other hand, writing unwrap() in production code is RETARDED
â„–21411[Quote]
>>21409>shill rust as a feature>not even good at the languageits over
>both sides are right.meds both sides are annoying as fuck and should get jobs
>on the other hand, writing unwrap() in production code is RETARDEDTSMT
â„–21412[Quote]
blaming rust/cloudflare devs using rust wrong is funny but retarded
say they handle the panic properly instead of crashing, then what? the program doesn't work without that config so they'd just have to exit anyway
â„–21414[Quote]
>>21412>the program doesn't work without that config so they'd just have to exit anywayjudging by how much cloudflare makes and how important their shit is they would have that trigger an alert to get every nigga up to fix it, they only found the bug hours later because they never actually bothered to make good error messages
â„–21415[Quote]
you can't just RUN 50% of the internet and not have a good monitoring stack that's retarded
â„–21418[Quote]
fuck rust, I have to learn it for my internship and only know python 💀
â„–21419[Quote]
>>21417Fill me in on what tsmt means
â„–21420[Quote]
>>21419true so much true or this so much this, don't remember
>>21418have fun lol, the official rust book is really nice
â„–21425[Quote]
>>21422you don't have to learn c first anymore nigga
its a fun language though