@fasterthanlime on one hand, cargo features are a petard we can use to hoist ourselves, on the other hand they let people get their work done on time, so impossible to say if they are bad or not
So I'm probably doing it wrong, right, but one of the (technical) downsides to nix is that I think it currently needs to fetch several gigabytes' worth of things from cache to finish evaluating and come to the conclusion that it.. doesn't need to do much at all?
@fasterthanlime@msfjarvis apologize for being slightly pedantic here: when using flakes, nix requires downloading all flake inputs transitively before it can evaluate derivations.
Derivation inputs are only downloaded when trying to build the derivation.
Unless IFD (input from derivation) is triggered, you technically don’t need toolchains present just to evaluate things (eg via nix build .# --dry-run).
Happy to take a look if crane seems to be at fault triggering IFD
