> enabled by a flag such as our --threads:on Global flags like these create dialects and don't work for composing libraries in general which stifles development - this is by and large a broken model that even C is trying to move away from (who remembers the mess of linking single-vs-multithreaded C std libs?)
In general, with regards to thread pools, what's really cool is when a language supports the primitives necessary to build thread pools outside of the language and the thread pool doesn't have to be distributed with the language itself - the primitives are unlikely to change, while thread pools continue to become better, inevitably making the old ones obsolete - it would be interesting to hear what _[minimal](https://forum.nim-lang.org/postActivity.xml#minimal) support you need from the language to build your thread pool - then everyone can choose whether to use a `Future[T]` based pool or not depending on the use case.
