If you read Badgrer's README carefully (and if Badger's README tells the truth), you'll see that Badger's transactions are implemented with sort of CAS: - transaction remembersall version of all data it reads, - on commit it rechecks that all data read during transaction were not modified, - transaction fails otherwise.
So, if Badger's transactions are really implemented that way, then there is no real need in CAS in level above Badger. Looks like Badger already implements serializable transactions using optimistic approach. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
