Re:Global Interpreter Lock, or how to kill it
by swannodette on Wednesday June 29, 2011 @04:23PM
(#2711109)
Clojure is designed for the user level and offers some unique advantages over Haskell's STM [1]:
* MVCC snapshot avoiding transactions restarts
on read invalidation.
* Ensure references on read-writes provides a
kind of manual control over resource acquisition order.
* Has explicit commute which reduces retries on
commutative writes.
[1] http://stackoverflow.com/questions/4560605/how-does-clojure-...EDIT: I didn't read the OP closely enough. Yes grafting fine-grained STM onto a imperative language hasn't born much fruit.
Re:Global Interpreter Lock, or how to kill it
by william42 on Wednesday June 29, 2011 @04:45PM
(#2711222)
Isn't Clojure still mostly functional and mostly based on persistent data structures?
Re:Global Interpreter Lock, or how to kill it
by calebmpeterson on Wednesday June 29, 2011 @05:50PM
(#2711540)
Yes very much so...and then some.
Agreed. The only project that I know of that's even close to a "working" implementation of STM is Haskell and that's because Haskell doesn't have uncontrolled stateful code.