It also has real type safety and thread safety.
It also has real type safety and thread safety.
Do tell.
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.
Rust crates have the second and third problems.
Rust at least has type annotation.
The type has private fields. There’s no constructor. There’s no implementation of the From trait except on itself. You can’t find a function anywhere that returns the type.
Then if Barabbas really was pardoned, to some of his acquaintances who didn’t know the pardon, he was sent off to die, but then showed up later in the weekend.
Maybe AI will boost open source development more than commercial development since open source devs don’t have the privacy concerns.
but why would you want to?
I visited a company that outsourced its IT to India. We were delayed 24 hours because the guy who could whitelist our computer on their network was asleep. It was the middle of the night where he lived.
Me: <starts a heredoc>
jetbrains: This heredoc goes on FOREVER!
Me: I’m going to close it…
jetbrains: <dies>
If you work at the same place long enough, you’re forced to remember over and over again.
real question: are vegan chefs ok with cooking eggs?
The chef eats the egg they botched the worst.
I think this is way off base. It’s easy to make yourself single.
Cheaters either think they will get away with it, or are lying to themselves about what they are doing.
“My partner won’t mind so much.”
“Nothing that feels so right could be wrong.”
“I’m not the kind of person who cheats, so considering the circumstances, this doesn’t really count.”
No you’re not wrong. There’s a reverse fallacy called the ludic fallacy: an unwarranted belief that the rules of the game describe how the game actually works.
“Given a fair table, if red comes up 99 times in a row, what are the relative odds of getting red vs. black?”
Mathematician, falling for the ludic fallacy: 1:1
Realist: You’re wrong. The table isn’t fair. Red is more likely.
However, people tend to underestimate how likely long runs are at a fair table.
And they were bums living in some other guy’s garden until they got caught.
What’s the meaning of a fractional “Degree of Kevin Bacon”?
Anthropogenic Global Mourning
An a380 is so big when it takes off it looks like it’s moving slow, just kind of hanging in the air