Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
[ ] problem 1
koch temp c -r testament/testament.nim r tests/test.nim
probably doesn't do what you thought it did:
it roughly calls:
koch temp
bin/nim_temp c -r testament/testament.nim r tests/test.nim
this doesn't use bin/nim_temp to run tests, for that you need --nim:bin/nim_temp (bin/nim_temp is only used here to compile testament/testament.nim)
when not defined(windows): # xxx: on windows, dots not properly handled, gives: `....2\n\n`
(ie, would work in cmdline line but not if compile command called indirectly via execCmdEx as may be the case with koch temp c -r testament/testament.nim r tests/test.nim
(replying to PM message)
koch temp c -r testament/testament.nim r tests/test.nimprobably doesn't do what you thought it did: it roughly calls: koch temp bin/nim_temp c -r testament/testament.nim r tests/test.nimthis doesn't use
bin/nim_tempto run tests, for that you need--nim:bin/nim_temp(bin/nim_tempis only used here to compile testament/testament.nim)[ ] problem 2 tests/test.nim is probably incorrect, should be tests/test/test.nim` according to https://github.com/nim-lang/Nim/pull/16698
[x] problem 3 running your command took 171s due to a regression I found thanks to looking into your use case https://github.com/nim-lang/Nim/issues/16703
[ ] problem 4 I can't reproduce your problem (annoying dot remains); maybe it's due to the same problem on windows as this: https://github.com/nim-lang/Nim/pull/16495#pullrequestreview-559581237
(ie, would work in cmdline line but not if compile command called indirectly via
execCmdExas may be the case withkoch temp c -r testament/testament.nim r tests/test.nim