> But as a new user, it feels strange that the default mode of Nim is > non-threaded, and that turning on thread support (with no other change) > breaks my code that interfaces with c in unexpected, non-obvious ways.
Well the library you use calls your code from a different thread, so `--threads:off` was a lie as far as the compiler is concerned. I don't know what we can do to improve the situation except that of course `--threads:on` will eventually be the default as more and more code runs multithreaded. Oh and and one more note: If the callback that you pass to C that then runs in a different thread is not declared as `.gcsafe` or `.thread` in the wrapper, the wrapper is broken.
