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;
    }
}
  • anyhow2503@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    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?

    • nightlily@leminal.space
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      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.

  • [object Object]@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    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.

      • bobo@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        3 days ago

        random pile of unclear errors

        warning: Git tree ‘/path/to/repo’ is dirty

        • Ephera@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 days ago

          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…

          • bobo@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            2 days ago

            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"
            
            • Ephera@lemmy.ml
              link
              fedilink
              English
              arrow-up
              0
              ·
              2 days ago

              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. 🥲

              • bobo@lemmy.ml
                link
                fedilink
                arrow-up
                0
                ·
                2 days ago

                For me there was only 1 line beneath that error, it’s more visible than the warning. Maybe they improved it, or you started reading from the top?

                I just completely forgot about that error because I have an extremely basic config.

                • Ephera@lemmy.ml
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  2 days ago

                  Hmm, that’s interesting. For me, it looks like this:

                  I actually thought, it said somewhere in there, that the file isn’t staged, but apparently not even that (anymore?).

                  You don’t happen to be using Lix or something, do you? I’ve heard that it’s supposed to have better error messages, but I was never sure how much better it might be…

                  Edit: Perhaps I should add that those code locations it shows, are not from my code. Only the modules/terminal/new_file.nix in the second-last line is relevant.

    • SpaceNoodle@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      Template errors make sense as long as you carefully read the entire error, but nobody has ever actually done that.