@bascule re: your most recent blogpost, you should read up on linear types and uniqueness typing. statically guarantee single owner
@reiddraper I'll check it out. Kilim was also able to statically guarantee only one reference is ever held to any object in an aggregate
-
-
@bascule afaik (I looked a while ago) go (lang) doesn't raise any exceptions or provide any safety in this regard. is that outdated? -
@reiddraper no idea... they claim to! o_O -
-
@reiddraper@mrb_bk I see, they describe it as a "convention", which means it's about on par with Celluloid :| -
-
@reiddraper@mrb_bk seeeeeeems bad -
@bascule@reiddraper didn't see the post yet but yeah, it's by convention. There's a "race detector" for goroutines and others in progress
End of conversation
New conversation -
-
-
@bascule good reference on linear typing: http://homepages.inf.ed.ac.uk/wadler/papers/linear/linear.ps … -
@reiddraper question is how to do this in a dynamic language :| -
@bascule yeah static checking will be tough. tho raising a runtime exception is still preferable to having unknown shared reference, imho
End of conversation
New conversation -
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.