461
rust blasphemy (added context)
(lemmy.world)
made in gimp, with <3
Context for actual rust programmers
I was having massive beef with the rust compiler yesterday, every cargo check takes 20 seconds.
And then look at the three functions below, only one of them are Send, if you know why, please let me know.
(Note: value that is not Send cannot be held across an await point, and Box is not Send)
async fn one() {
let res: Result<(), Box<dyn Error>> = do_stuff();
if let Err(err) = res {
let content = err.to_string();
let _ = do_stuff(content).await;
}
}
async fn two() {
let res: Result<(), Box<dyn Error>> = do_stuff();
let content = if let Err(err) = res {
Some(err.to_string())
} else {
None
};
drop(res);
if let Some(content) = content {
let _ = do_stuff(content).await;
}
}
async fn three() {
let content = {
let res: Result<(), Box<dyn Error>> = do_stuff();
if let Err(err) = res {
Some(err.to_string())
} else {
None
}
};
if let Some(content) = content {
let _ = do_stuff(content).await;
}
}
I get that it's supposed to be a meme, but aside from the first one these aren't even rust stereotypes. Is this a meme specifically for people who haven't used rust, know nothing about rust but have maybe heard that it's a programming language?
Yeah, part of the point of Rust is that it does exactly what you tell it - sometimes to the point of absurdity. No implicit casting for instance.
And here I was thinking most of our programming problems come from the thing doing exactly what we told it to, but didn't quite think the process through enough. Or at all.
This is for people who learnt C++ in 2008 and refuse to believe that they've never fucked up a malloc in their lives
Hah I learned c++ in the 90s and never felt shame for messing up an allocation.
I think when this happens, I have a puddle of memory, the spilled ram “lubricates” the pointers, which often rub against each other. The wasted memory acts like oil does to a rusted chain. It’s helping push the program through the finish line.
Yes, I am having fun here
I mean Rust is definitely known for long compilation times but yeah otherwise I am not sure how any of this is Rust-specific. Maybe by "doesn't do what you tell it to do" they mean the borrow checker and strict compile time checks...?
i've edited the post content for context, and a small puzzle for rust programmers
I was actually wondering if this was supposed to be about a specific problem someone has with rust (not like I haven't gotten stuck on some weird corner with rust before), but looking at the meme, that seemed unlikely to me. Thanks for the context.