4 ms·
Every pure function is part of a bigger machine that's eventually mutable state, or by definition that pure function has no reason to exist. Ergo, cache invalid
by LogicUpgrade 5y ago
Every pure function is part of a bigger machine that's eventually mutable state, or by definition that pure function has no reason to exist. Ergo, cache invalidation is hard.
- coldtea 5y ago>Every pure function is part of a bigger machine that's eventually mutable state, or by definition that pure function has no reason to exist Not necessarily. The universe could be just one huge pure function.
- kevincox 5y agoBut the universe is constantly changing. So you will need to know the specific bits of the universe that your function depends on or you will never get a hit.
- loopz 5y agoIs the universe changing, or just your references to it?
- LogicUpgrade 5y agoSo the references are mutable. Gotcha.
- loopz 5y agoAye, functional core, imperative shell (us!).
- breischl 5y agoHa, I guess it's possible. But if that's true then it seems that some of the intermediate steps in "public static void universe()" use mutable state that can result in cache invalidation difficulties.
- Dylan16807 5y agoI don't follow. Being part of a bigger machine isn't proof that it's hard.