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<dyn Error> 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;
}
}
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.
Yes, preferring a language that’s easy to read and therefore easy to maintain over a language like Rust is definitely coping 🙄
preferring Rust over Rust? what do you mean?
do you think loosely typed python is easy to read and maintain?
I’ll stick with Go TYVM
Yeah, like, who would ever want to
stuff1()?.map(stuff2);It’s much better to just:
err, value = stuff1(); if err == nil return err, nil; if value != nil stuff2(value);And you might even:
for a in vec { vec[a] }Ah yes, the good old random pile of unclear errors because you forgot to add the file in git thanks nix
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:
It even gives you
Is this a comment I’m not flake enough to understand?