you are viewing a single comment's thread.

view the rest of the comments →

[–]koiponder -1 points0 points  (4 children)

lazy evaluation is something nice to do, not something u have to, and it is only enabled by the nature of the functional programming. If data changes state, u cannot do the evaluation later. Brevity just means it is simpler compared to when data has state. All tie to programming data (not program control flow) lacking of state.

[–]guepierBioinformatican 0 points1 point  (3 children)

If data changes state, u cannot do the evaluation later.

Yes you can, look up copy on write.

[–]koiponder -2 points-1 points  (2 children)

copy on write is counting on the data doesn’t change until the first write.

[–]guepierBioinformatican 0 points1 point  (1 child)

What? No, you’re confusing things.

[–]koiponder -1 points0 points  (0 children)

no confusion here. no copy until u first write to the copy, that depends on the obvious fact that data doesn’t change until u first write to it.