Concurrent code and expensive instructions
Concurrent code and expensive instructions
Posted Jan 28, 2011 16:15 UTC (Fri) by nix (subscriber, #2304)In reply to: Concurrent code and expensive instructions by PaulMcKenney
Parent article: Concurrent code and expensive instructions
Sounds almost exactly like Haskell monads, if 'everything that could change' is set equal to 'the entire world'. (Of course monads were invented precisely to transform those annoying side-effects into nice clean function parameters, so this is not at all surprising.)
