As a beginner with knowledge of only F# and Clojure, I feel a lot of his issues are solved with having immutable values.
> It's theoretically possible that the 'f()' or 'x' might change between the lazy evaluation of step one and the lazy evaluation of step three million. Trying to prevent that is what we programmers call a 'hard' problem.
and the examples he gives in Myth 3 & Myth 4 where he reassigns `x` to mean something else. Both of these can be avoided had x been immutable.
I agree with the conclusion in Myth 2. I didn't understand the latter half of Myth 3, so can't comment on that.
Am I missing something wrt my assumption of immutable values solving most of the issues?
> It's theoretically possible that the 'f()' or 'x' might change between the lazy evaluation of step one and the lazy evaluation of step three million. Trying to prevent that is what we programmers call a 'hard' problem.
and the examples he gives in Myth 3 & Myth 4 where he reassigns `x` to mean something else. Both of these can be avoided had x been immutable.
I agree with the conclusion in Myth 2. I didn't understand the latter half of Myth 3, so can't comment on that.
Am I missing something wrt my assumption of immutable values solving most of the issues?