How Inko Does Safe Concurrency

In my last article on Inko, I implemented several data structures to demonstrate how Inko’s single ownership model works. In this article, I will expose a big lie in that article and also dive into how Inko safely handles concurrency. Why Concurrency is Hard Truth be told, concurrency is hard for a lot of reasons, but the one that comes up most often is concurrent memory access. If you have two threads of execution running at the same time, and they both read from and/or write to a variable, the variable is likely to end up with incorrect or garbage data.

Continue reading