Thank you @ynfle, I did not know about --verbosity. Unfortunately, that makes name even more verbose (duh!) so it makes the "problem" (if you can call it that) even worse. Using --hint:source is better, but it does not seem that it works in combination of --hints:off? What I'd like is to minimize the (non warning / error related) hints but get the actual line of code that caused the error or warning on nim's output. Is that possible?
Thank you as well for the "include prelude" hint. I was using "import prelude". I have some thoughts about that but that can go into a separate thread. Regarding the debugging experience, I have not tried nim_gdb. Does it work on windows? IMHO what would really take nim to the next level (debugging wise) would be to get debugging support on VS Code.
