@KirinDave I'm not sure you understand what I mean by "capability". I'm coming from a capability-based security perspective
-
-
Replying to @KirinDave
@KirinDave I think degradation is the central idea behind capabilities1 reply 0 retweets 0 likes -
Replying to @KirinDave
@KirinDave haha, please don't interpret degradation as an insult ;) Mutable references are capable of mutation, simple as that1 reply 0 retweets 0 likes -
Replying to @KirinDave
@KirinDave mutated by the CPU into L1 cache before the memory controller flushes it to main RAM? Not sure what you're asking here2 replies 0 retweets 0 likes -
Replying to @KirinDave
@KirinDave I'm a fan of isolation of mutable state via ownership transfer between actors/concurrency primitives (see D, Kilim, Go)2 replies 0 retweets 0 likes
Replying to @KirinDave
@KirinDave @boundary explicit support for volatile, and explicit synchronization via mutexes where needed
3:08 PM - 24 Sep 2012
0 replies
0 retweets
0 likes
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.