@KirinDave I'd prefer a capability-based model where you have mutable and immutable views of the same data
@KirinDave I'm a fan of isolation of mutable state via ownership transfer between actors/concurrency primitives (see D, Kilim, Go)
-
-
@bascule Good for you and I, but not what everyone needs. @boundary cannot accept that overhead. What now? -
@KirinDave @boundary explicit support for volatile, and explicit synchronization via mutexes where needed
End of conversation
New conversation -
-
-
@bascule So we start with the simplest defintiion "immutability" and work our way out from there. Its the path of least resistance.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.