> They already took a few steps inside of Go to try to ensure that concurrency is quite non-deterministic I would not be surprised as they are already proactiv

> They already took a few steps inside of Go to try to ensure that concurrency is quite non-deterministic I would not be surprised as they are already proactively ensuring things like map ordering are randomised so that people just can't rely on some deterministic ordering: run the example code here[0] multiple times and it produces not just a seemingly random result (as would be for a typical hash table) but a truly different result for each run. [0]: https://nathanleclaire.com/blog/2014/04/27/a-surprising-feature-of-golang-that-colored-me-impressed/ https://nathanleclaire.com/blog/2014/04/27/a-surprising-feat...