mirror of
https://github.com/NixOS/nix
synced 2025-07-07 22:33:57 +02:00
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.
This commit is contained in:
parent
ac0fb38e8a
commit
d0f2da214b
6 changed files with 25 additions and 3 deletions
|
@ -0,0 +1 @@
|
|||
42
|
Loading…
Add table
Add a link
Reference in a new issue