How is this not resulting in infinite recursion?

[SymphonySimper]

Here home.activation is referring to config.home.activation, shouldn't this cause infinite recursion?

    home.activation =
      let
        name = "myCopy";
        # filter is not required, but it's here to make sure nothing funky happens
        entries = builtins.filter (entry: entry != name) (builtins.attrNames config.home.activation);
      in
      {
        ${name} = lib.hm.dag.entryAfter entries (

Source: https://github.com/SymphonySimper/.dotfiles/blob/main/modules/home/copy.nix#L73-L80

[rycee]

I would think it works because entries only observes the attribute names of config.home.activation, not the corresponding values. If entries was defined so that it also observed the value, then it should produce infinite recursion.

So, something like the following hypothetical definition would probably cause problems:

entries = filterAttrs (n: v: n != name && v != null) config.home.activation;

[SymphonySimper]

Understood, thanks!

[rycee]

Great, apologies for the late answer 🙂

And if you want to know more about this behavior, which sometimes can be tricky to follow, then some keywords are "lazy evaluation", "non-strict evaluation", and "call-by-need".

[SymphonySimper]

Great, apologies for the late answer 🙂

No apologies necessary! 😅 I was just curious why it was working.

And if you want to know more about this behavior, which sometimes can be tricky to follow, then some keywords are "lazy evaluation", "non-strict evaluation", and "call-by-need".

I'll look that up. Thanks again for the response!