2 ms·
I don't follow you. When people say "you can run these functions in any order" (or "in parallel"), how do you interpret this to also imply "...regardless of the
by the_af 11y ago
I don't follow you. When people say "you can run these functions in any order" (or "in parallel"), how do you interpret this to also imply "...regardless of their input"?
Why does it matter if they say "run" instead of "evaluate"? What's the difference, in your opinion?
Do people really have trouble with the (universal, not FP-specific) notion that the input to a function matters?
Do we both agree that FP/immutability doesn't promise what the author of the article thinks it promises, and that people (regardless of about how clearly they say it) do not claim it does?
- coldtea 11y ago>Why does it matter if they say "run" instead of "evaluate"? What's the difference, in your opinion? "Evaluation" solely implies passing an actual value and getting the result from a function. Taken in isolation, each evaluation (of pure functions) is independent from whether 10 or 200 other happened before or after -- it depends only on the input it gets. Saying "run" on the other hand can be conflated to mean running a pure function in the course of a program's execution, and there the order or execution can matter with regards to the overall program's behavior, e.g. when it affects the derived input of a subsequent function. >Do people really have trouble with the (universal, not FP-specific) notion that the input to a function matters? Yes, people do expect pure functions will free them from race conditions for example -- only to discover that they still exist, as the author did, at a higher conceptual level. Heck, if we are to discuss the original article, isn't it a given that such people as its author do exist and have the same confusion? Or does the author seem like some totally ignorant programmer that is not representative of more people (and that we'd expect him/her to get it all wrong)? It doesn't come out that way to me.