Skip to content

builtins.derivationStrict #9701

@roberth

Description

@roberth

Problem

derivationStrict is not mentioned in the manual.

Should it be documented? Yes, because it is arguably a better function than derivation:

  • it is at least as capable as derivation
  • it doesn't return its arguments unnecessarily (blurring what's the actual interface of a package)
  • it's more efficient because it does less unnecessary attrset stuff
  • its returned attrNames are more predictable than those of derivation and (by extension) Nixpkgs mkDerivation,
    • permitting more laziness when wrapped sensibly (not widely relevant, but even a couple percent of instantiations saved is a win)

Proposal

Document the derivation arguments on a separate page about derivations. This page is store-level documentation.
Document both builtins as usual, referring to the derivation page, and a paragraph about the return value and how it relates to the outputs argument.

Checklist

Priorities

Add 👍 to issues you find important.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationlanguageThe Nix expression language; parser, interpreter, primops, evaluation, etc

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions