hintProcessing dot interference issue on windows
timotheecour opened this issue · comments
replying to PM message regarding problems with koch temp c -r testament/testament.nim r tests/test.nim
- 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)
-
problem 2
tests/test.nim is probably incorrect, should be tests/test/test.nim` according to nim-lang#16698 -
problem 3
running your command took 171s due to a regression I found thanks to looking into your use case nim-lang#16703 -
problem 4
I can't reproduce your problem so it's probably windows only (annoying dot remains); maybe it's due to the same problem on windows as this:
nim-lang#16495 (review)
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