From b31f930e5f16ad66098334b901714500ce2474d6 Mon Sep 17 00:00:00 2001 From: Dani Date: Mon, 11 May 2020 23:49:18 +0200 Subject: [PATCH] Add missing word --- pills/12-inputs-design-pattern.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pills/12-inputs-design-pattern.xml b/pills/12-inputs-design-pattern.xml index 15af229..5612657 100644 --- a/pills/12-inputs-design-pattern.xml +++ b/pills/12-inputs-design-pattern.xml @@ -44,7 +44,7 @@ The nix reference for packages is nixpkgs, a single repository of all descriptions of all packages. I find this approach very natural and attractive for new contributions. - For the rest is chapter, we will adopt the single repository technique. The natural implementation in Nix is to create a top-level Nix expression, and one expression for each package. The top-level expression imports and combines all expressions in a giant attribute set with name -> package pairs. + For the rest of this chapter, we will adopt the single repository technique. The natural implementation in Nix is to create a top-level Nix expression, and one expression for each package. The top-level expression imports and combines all expressions in a giant attribute set with name -> package pairs. But isn't that heavy? It isn't, because Nix is a lazy language, it evaluates only what's needed! And that's why nixpkgs is able to maintain such a big software repository in a giant attribute set.