>.unwrap()
.unwrap()
Levi Gutierrez
Owen Gonzalez
good. I hate hidden error paths.
Jason Roberts
>Using unwrap
>Not matching like a chad.
ngmi
Liam Sanchez
>errno = 0; int res = func(); if (!res) { perror("error calling func()"); exit(1) }
Tyler Gray
using std::optional;
template
struct based_optional : optional {
using optional::optional;
operator T() {
return **this;
}
};
Jayden Price
what an ugly language
Asher Morales
>not using match, ? operator or unwrap_or
Jose Barnes
Like i have time to decipher all these Ts, asterisks and semicolons and shit
Parker Sanders
Rust is hardly any better, the crazy symbols are just in different places.
Ryder Wright
Oh i thought that was rust
Lucas Hill
that's seeples, mate
Hunter Collins
rust is nice
go is ugly
Bentley Mitchell
No one writes C++ like that in the industry. Rust programmers do though.
Carson Butler
C++ like what? Templates? Are you serious?
Jeremiah Garcia
That's "modern C++" and it looks exactly as shit as Rust
Camden Sullivan
nooooooo you can't just unwrap, you need to error check!!!!
Julian Stewart
Wait until you see modern golang with the if err == nil everywhere
Or modern C with unreadable macro spam and (void *) casts everywhere
Dylan Bell
>unreadable macro spam and (void *) casts everywhere
so...C?
Gavin Clark
who calls a programming language the same as a fungi nobody wants
Angel Jenkins
This guy thinks metal rust is a fungi
Andrew Howard
It's no different from letting a function throw an uncaught exception in another language. Rust just makes it explicit.
Jeremiah Jenkins
There is, in fact, a fungus called the rust fungus. And the rust programming language is named after it.