You are right. But it's not needed in Lobster, because threading model is different. It doesn't have concurrent access problems: > Lobster built-in multi-threa

You are right. But it's not needed in Lobster, because threading model is different. It doesn't have concurrent access problems: > Lobster built-in multi-threading functionality ... is different from multi-threading in most other languages, in that it does not allow threads to share memory or any other VM state. http://aardappel.github.io/lobster/language_reference.html#multi-threading http://aardappel.github.io/lobster/language_reference.html#m...