Skip to content

attrsets: clarify that mapAttrs maps over *leaf* attrs #212189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roberth merged 2 commits into from Jan 25, 2023
Merged

attrsets: clarify that mapAttrs maps over *leaf* attrs #212189

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee00af7
attrsets: clarify that mapAttrs maps over *leaf* attrs
Jan 22, 2023
a4e3e16
Update lib/attrsets.nix
Jan 25, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions lib/attrsets.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -480,8 +480,13 @@ rec {


/* Like `mapAttrs`, except that it recursively applies itself to
attribute sets. Also, the first argument of the argument
function is a *list* of the names of the containing attributes.
the *leaf* attributes of a potentially-nested attribute set:
the second argument of the function will never be an attrset.
Also, the first argument of the argument function is a *list*
of the attribute names that form the path to the leaf attribute.

For a function that gives you control over what counts as a leaf,
see `mapAttrsRecursiveCond`.

Example:
mapAttrsRecursive (path: value: concatStringsSep "-" (path ++ [value]))
Expand Down