> Yeah, choosenim currently does not support 64bit. Then I'll have to wait. Is there an estimate about when it might support it?
As for my setup, I'm really confused. I did follow all instructions, and GCC is available on PATH, and Nim too — and really, there isn't much to the setup to be done. I've compiled quite a few code examples, and they seem to work. Nimble succesfully installed dependencies. It's only the tests that fail (both Nimble and koch, the latter with Cpp tests mainly). So, somehow (from koch tests) it looks like there are quite a lot of test failures when it comes to C++. I'm not sure how bad this can be, but I guess that sooner or later I'll be banging against some limits. Could it just be that the tests are not tuned for Win 10 x64? Or, I wonder, if the Fall Creators Update introduced breaking changes... Anyhow, for now I'll play around with Nim some more, and go over the book exercises again; I'll still be benefiting from learning the basics. Of course, I can just move to my other Linux machine, but I was hoping to use Nim to create DLLs to use with other languages. To be honest, my worry is just that in the past I came across quite a few great and robust languages (like Haskell, to name one) that never seem to work 100% under Windows (there are always problems with some libs, dependencies, or compiling DLLs, etc.) despite the years they've been around in stable release. In the last years many huge leaps have been achieved in cross-platformness, and this is really great; but with Windows there are always pitfalls round the corner, and often cross compiling from Linux seems the better choice. Learning a new language (especially if it involves a shift in paradigms from the languages one has worked with) is already a challange, but when there are issues related to the environment then it's difficult to pinpoint if the problems are due to one's lack of knowledge or to issues with the OS. Thanks for the help Dom!
