Nim has thread support natively. And an async implementation in it's standard library which is made entirely as a library, so you're free to write your own, in fact there exists alternative implementations of async/await in Nim. Just the fact that a feature like this _can_ be implemented as a library is a testament to how powerful of a language Nim is.

It's not my area but, surely concurrency can be added, and why does it need to be native? Surely a library is fine.

(I chose not to learn go because of it's lack of generics and exceptions. It seemed like a huge step backwards)

Related article on Nim concurrency: https://onlinetechinfo.com/concurrency-and-parallelism-in-ni...

Why do you say that?

It's far from perfect but it does work (and has for a few years), and it helps you by requiring proof that actions are disjoint. There is work now on including Z3 which would work this much smarter.

https://nim-lang.org/docs/manual_experimental.html#parallel-...