Rust output is bad? I feel like it's one of the best in terms of telling you where you got things wrong. Nix output when you accidentally get infinite recursion is so bad.
Come to think of it, Nix fits all three better than Rust.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rust output is bad? I feel like it's one of the best in terms of telling you where you got things wrong. Nix output when you accidentally get infinite recursion is so bad.
Come to think of it, Nix fits all three better than Rust.
People who've never used Rust or only used it once and couldn't grok it like to meme that Rust is bad to cope.
Ah yes, the good old random pile of unclear errors because you forgot to add the file in git thanks nix
random pile of unclear errors
warning: Git tree '/path/to/repo' is dirty
Unfortunately, that shows up even when you've just modified an existing file, which is not a problem for it.
And which also happens to be the state my repo is in basically all the time, because I'll change some setting, then see if it works like I want it to before making a commit...
Fortunately, your comment is not relevant at all since I incorrectly posted the warning instead of the explicit error:
error: Path 'path/to/file' in the repository "/path/to/repo" is not tracked by Git.
It even gives you
To make it visible to Nix, run:
git -C "/path/to/repo" add "path/to/file"
I thought, you posted about the warning, because that's actually easier to see than the error. Because yeah, it does say what you posted, but it's in the middle of like 30 lines of other stuff. When I forget to stage a new file, it almost always takes me 5+ seconds to spot what the problem is. 🥲
Is this a comment I'm not flake enough to understand?
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.
output makes no sense
C++ template errors enter the room
Template errors make sense as long as you carefully read the entire error, but nobody has ever actually done that.
You are saying that the error messages terminate at some point?
boost::msm errors enter the room
Deterministic: ✅ ❌
Deterministic when hit by that weird cosmic ray: ❌❌
/jk
So a narrow but clear win for the Rust compiler still...
cargo() {
cargo $@
echo So how you doin\' today?
}
Fixed
I thought the rust compiler was supposed to be polite and helpful (unlike gcc, or nix).
It is, this meme is just trash.
Oh god nix output
You create a new file and don't check it into git yet.
Nix commands: "I've never met this file in my life!"
gcc was unhelpful a couple decades ago. I've found it to be rather helpful in recent years.
Yeah, recent versions of GCC have gotten a lot better. I suspect it’s actually because of languages like Rust raising the bar.
cargo delete this_post
You are running into the Send Approximation being too conservative. The compiler does not like to see a let binding for a non-Send type and an .await statement in the same scope. It is not (yet) smart enough to know that the non-Send type is already consumed by the time of the .await.
You've already discovered the workaround in your three(). To make it more concise
async fn four() {
let content = do_stuff().err().map(|err| err.to_string());
if let Some(content) = content {
let _ = do_stuff_2(content).await;
}
}
I love the rust compiler, it makes debugging so easy
Just a guess, but are you missing + Send on your error type?
Yeah, I was gonna say, that might be the root cause.
In the vast majority of cases, you want Box<dyn Error + Send + Sync>, but folks tend to leave out the Send + Sync, because it looks like additional complexity to them, and because it doesn't cause problems when they're not doing async/await.
It's better to define a type alias, if you don't want that long type name everywhere.
This is an awful "meme"
sometimes?! Cargo never makes sense to me!
First mistake was using async
It never asks me :(