Thanks everybody for contributing to this discussion! Eventually I think I will leave the NimraylibNow! situation as-is. I really have to control the order in which `windows.h` is included into the generated C file from Nim. Maybe in a year or two we will be free from the hegemony of `windows.h` but for now I will endure the suffering.
I made an attempt to get free from `windows.h` and it failed <https://github.com/greenfork/nimraylib_now/pull/54>. The problem is that I need to absolutely make sure that `windows.h` is included only after my C file. There are several `#define` declarations that control what is included in `windows.h`, for Raylib necessary ones are here <https://github.com/raysan5/raylib/issues/1217#issuecomment-618428626>. So if `windows.h` is included before my C file with all these `define` declarations, I'm in no luck. And since there's no specification on the order of inclusion, if I pursue this way, it may as well break in the next Nim release or just by passing `--threads:on` flag (as practice shows `--threads:on` can also alter the order of includes <https://github.com/greenfork/nimraylib_now/issues/50)>.
