3 ms·
Not only bets are off in non-functional language, it's the wrong solution. STM puts the cost of locking into everything, ie slower default operations, whilst s
by rurban 6y ago
Not only bets are off in non-functional language, it's the wrong solution.
STM puts the cost of locking into everything, ie slower default operations, whilst still being concurrency unsafe. Deadlocks can occur.
There are proven good solutions for fast and safe concurrency with ownership tracking and a good compiler/scheduler. No, not Rust. And not STM. We fought with this for years.
- rrss 6y ago> There are proven good solutions for fast and safe concurrency with ownership tracking and a good compiler/scheduler. Do you have any pointers to these solutions for the uninitiated?
- rurban 6y agoAll concurrency-safe languages. Eg pony, concurrent pascal, the parrot vm, ...
- amelius 6y agoEh, STM is often used as a solution to avoid locking. https://en.wikipedia.org/wiki/Software_transactional_memory https://en.wikipedia.org/wiki/Software_transactional_memory
- brandmeyer 6y agoIf you read into the implementation papers a little more deeply, you'll find that they are typically implemented with locks under the covers.