Scala STM Discussion

Oh, this is good news :-). And thanks for the link! con...@sciss.de schrieb am Donnerstag, 11.

All right, I see. Thanks :-) Am Montag, 4. Dezember 2017 18:24:23 UTC+1 schrieb Nathan Bronson: Hi

So this would be my "improved" version which closes the databases which will possibly run

Hi, I am running a set of instructions in STM.atomic block. There are some conflict transaction and

Hi, We are planning to use ScalaSTM for our java application to protect the data. I wanted to know if

Hi Nathan, thanks for looking into this. PLease find my comments below. Am Donnerstag, 4. Dezember

Hi, I've updated an old port to Scala I did of Rich Hickeys clojure's Ant Colony demo. It now

Hi Nathan, Thanks so much for the comprehensive answer. Given what you've said, I'm slowly

Jianbo, ScalaSTM internally supports partial rollback when there are nested transactions, although

I suggest Txn.retryFor(1, TimeUnit.NANOSECONDS). The first time it is encountered it will act like

Many thanks for your reply and the insights given. Regards – Matthias On Saturday, March 8, 2014 4:31

Nathan, Many thanks for the clarifications. The original comment is now also clear as it stands. I

Wow, a detailed an impressive reply. Thank you very much :)

Heliu, Perhaps it's reached the point where it does everything that anyone would want, and has no

Thanks. That makes perfect sense. On Monday, June 10, 2013 1:15:38 PM UTC-4, Nathan Bronson wrote:

Hi, I am trying to implement a lock(like basic read-write lock) based on the TMap. object TMapLock {

Lixing, Using afterCompletion like this calls unlock at the right time, but it is unsafe for another

You are right that a transaction that modifies the map and a transaction that makes a snapshot will

Yarco, Why are you trying to defer the commit? ScalaSTM is performing conflict resolution and retries

Thanks! On Sunday, 17 February 2013 22:39:29 UTC+1, Nathan Bronson wrote: Felix, You'll probably

In Scala < 2.10 the immutable.TreeMap's iterator produced a lot of garbage, which

Great. I have a test that can reproduce a race condition we run into when we save our event in

You can use val cause = Txn.OptimisticFailureCause(category, trigger) NestingLevel.root.

Yes, it will be released. The stack is unwound with an exception, so monitors are released and

You're right, the parameter is more specific than necessary. I've published 0.8-SNAPSHOT with

My opinion is that toString should return a transactionally correct value, and that there should be

Thanks Nathan, I got it to compile after I supplied scala-library.jar and it works now: final Map<

Hi Nathan, thanks for the advice and useful tip. Cheers, Lee On Thu, Dec 6, 2012 at 9:09 AM, Nathan

I'd be excited to see what can be done with macros and scala-stm; that would still not touch the

Thanks for the suggestions. For the second solution, I have the impression it's only practical