Yes, I understand that you are clarifying. I find that level of reasoning pedantic, and those who argue that point as if software can't possibly work correctly without it are ignoring their editor as they type.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
As in my other tweets, I use Scala in a very immutable way, but not entirely immutable because actors save me some problems by preventing races. Still, I prefer to use a case class to maintain immutable state at the instance level because it frees my mind from mutability burden.
Yeah, that's a reasonably good approach, and Scala facilitates it well. Your state is at least all in one place. There is nothing to stop you mutating global state defined elsewhere, except convention, though.
-
-
Agreed, but that's Scala no matter with actors or without.
-
Yes, absolutely.
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
And Haskell doesn't prevent you from deriving new immutable state from the same source immutable state simultaneously, and this causing a bug.
- Show replies
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.