Re: The cint == int != int trap

[chrisheller]

You can run something like 
    
    
     nim check --cpu:i386 mynimfile.nim

and target different architectures, etc without actually having nim run the C 
compiler. I have done that before to catch Windows bugs when I was on a Mac 
that was not setup for cross-compiling. See 
[https://nim-lang.org/docs/nimc.html](https://nim-lang.org/docs/nimc.html)

I haven't tried that with your specific example though. Can you try that and 
see if it catches it?