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;
    }
}
  • bobo@lemmy.ml
    8·
    4 days ago

    random pile of unclear errors

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

    • Ephera@lemmy.mlEnglish
      3·
      4 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
        2·
        4 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.mlEnglish
          2·
          4 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
            1·
            4 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.mlEnglish
              1·
              4 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.

              • bobo@lemmy.ml
                2·
                4 days ago

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

                It’s a different error. To me it looks like you tried to import a file that doesn’t exist. I made the file correctly and imported it, just didn’t git add it. After committing I switched without issues.

                Only the modules/terminal/new_file.nix in the second-last line is relevant.

                For me that error message was in the same spot. The rest of the trace is what was evaled so you got to that error. It’s the same principle as stack trace in other languages.

                You don’t happen to be using Lix or something, do you?

                No, unstable nixos + home-manager. The error above was from

                sudo nixos-rebuild switch --flake ...
                • Ephera@lemmy.mlEnglish
                  1·
                  4 days ago

                  Hmm, that sounds exactly like my setup. Weird.

                  I did have the file created, with {} inside (empty Nix expression). If I git add it, it works as well:

                  And yeah, I understand that it’s supposed to be a stacktrace, but other error messages look similarly horrendous and I can often only try to guess what’s wrong by reading the stacktrace top-to-bottom, so I’ve somewhat gotten used to doing that.

                  But good to know that these terrible error messages might be a problem with my system. Thanks!

                  • bobo@lemmy.ml
                    1·
                    4 days ago

                    I think we’re doing different things, that’s why it’s giving us completely different errors.

                    I just added files to imports in configuration.nix

                    I’m guessing you’ve got some manual error checking implemented with assertions?

                    error:
       … while calling the 'seq' builtin
         at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:402:18:
          401|         options = checked options;
          402|         config = checked (removeAttrs config [ "_module" ]);
             |                  ^
          403|         _module = checked (config._module);

       … while evaluating a branch condition
         at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:305:9:
          304|       checkUnmatched =
          305|         if config._module.check && config._module.freeformType == null && merged.unmatchedDefns != [ ] then
             |         ^
          306|           let

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: Path 'nix/bobo/test.nix' does not exist in Git repository "/home/bobo/dotfiles".
Command 'nix --extra-experimental-features 'nix-command flakes' build --print-out-paths '/home/bobo/dotfiles/nix#nixosConfigurations."bobo".config.system.build.nixos-rebuild' --no-link' returned non-zero exit status 1.

                    I can often only try to guess what’s wrong by reading the stacktrace top-to-bottom, so I’ve somewhat gotten used to doing that.

                    I’m yet to see any nix error be more readable top to bottom. And I think it’s intentionally designed that way so you don’t need to scroll up.