lix/tests/functional/lang/eval-okay-foldlStrict-lazy-initial-accumulator.nix

# Checks that the nul value for the accumulator is not forced unconditionally.
# Some languages provide a foldl' that is strict in this argument, but Nix language does not.
builtins.foldl'
  (_: x: x)
  (throw "This is never forced")
  [ "but the results of applying op are" 42 ]
primops: make nature of foldl' strictness clearer * Clarify the documentation of foldl': That the arguments are forced before application (?) of `op` is necessarily true. What is important to stress is that we force every application of `op`, even when the value turns out to be unused. * Move the example before the comment about strictness to make it less confusing: It is a general example and doesn't really showcase anything about foldl' strictness. * Add test cases which nail down aspects of foldl' strictness: * The initial accumulator value is not forced unconditionally. * Applications of op are forced. * The list elements are not forced unconditionally. 2022-10-15 23:32:55 +00:00			`# Checks that the nul value for the accumulator is not forced unconditionally.`
chore: rebrand Nix to Lix when it makes sense Here's my guide so far: $ rg '((?!(recursive).) Nix (?!(daemon\|store\|expression\|Rocks!\|Packages\|language\|derivation\|archive\|account\|user\|sandbox\|flake).))' -g '!doc/' --pcre2 All items from this query have been tackled. For the documentation side: that's for https://git.lix.systems/lix-project/lix/issues/162. Additionally, all remaining references to github.com/NixOS/nix which were not relevant were also replaced. Fixes: https://git.lix.systems/lix-project/lix/issues/148. Fixes: https://git.lix.systems/lix-project/lix/issues/162. Change-Id: Ib3451fae5cb8ab8cd9ac9e4e4551284ee6794545 Signed-off-by: Raito Bezarius <raito@lix.systems> 2024-05-14 00:05:08 +00:00			`# Some languages provide a foldl' that is strict in this argument, but Nix language does not.`
primops: make nature of foldl' strictness clearer * Clarify the documentation of foldl': That the arguments are forced before application (?) of `op` is necessarily true. What is important to stress is that we force every application of `op`, even when the value turns out to be unused. * Move the example before the comment about strictness to make it less confusing: It is a general example and doesn't really showcase anything about foldl' strictness. * Add test cases which nail down aspects of foldl' strictness: * The initial accumulator value is not forced unconditionally. * Applications of op are forced. * The list elements are not forced unconditionally. 2022-10-15 23:32:55 +00:00			`builtins.foldl'`
			`(_: x: x)`
			`(throw "This is never forced")`
			`[ "but the results of applying op are" 42 ]`