Maybe she really worked at Carl's Jr.
dudinax
joined 2 years ago
The first rule of the road is "right-of-way won't help you when you're dead".
"Lefty Loosey righty tighty"
One arrow points up to the left, one points down to the left.
Thanks, I've save your comment. I haven't heard of any of these.
It also has real type safety and thread safety.
Here's some of my personal complaints. I don't in general know how to fix them.
-
proc_macros need their own crate
-
generics cause problems. Many useful macros can't handle them. Try using a generic that's a complex async function, then pass a closure to it.
-
There's this kind of weird mismatch where sometimes you want an enum wrapping various types, and in others generics. I find my data flows switching back and forth.
-
async in rust is actually really good, but go does it better. I don't think rust could match go without becoming a different language.
-
Traits are just a big mess. Trait implementations with generics have to be mutually exclusive, but there aren't any good tools to make them so. The orphaned trait rule is necessary to keep the language sane but is incredibly restricting. Just today I find certain a attribute macros for impls that doesn't work on trait impls. I guess I have to write wrappers for every trait method.
-
The "new type" pattern. Ugh. Just make something like a type alias that creates a distinct type. This one's probably easy to fix.
-
Cargo is truly great, but it's a mystery to me right now how I'm going to get it to work with certain packaging systems.
To me, Rust is a bunch of great pieces that don't fit together well.
Rust. It's a qualitative improvement over the old ways.
The future won't belong to Rust itself, but one of its descendants. Rust is too clunky to be the ultimate expression of its best ideas.
The day Trump flip-flopped on Tik Tok, my wife's feed started to carry humanizing Trump videos. They've since disappeared.
No, u/dirthawker0 is supporting your point.
Good job anon. No good deed goes unpunished.