Closed SolitudeSF closed 1 month ago
Hello,
It's strange, it doesn't happen in my side. Are you using nim v2.0.2 ?
I will modify BuilderFlags.MergeStderr, this will resolve the problem (i intended to move this code section either way)
In fact, that is rather strange it worked in my side after looking at the problem :-D
Last version should fix it, please let me now if it doesn't
it does fix it. im using devel
. it is strange, i would imagine enum overloading should take care of this.
Cool it works.
It is bad design on my part, so in fact nim devel might be right. Having both ProcOption.MergeStderr and BuilderFlags.MergeStderr is quite bad.
But with {.pure.} pragma, it is better acceptable.
(I have also used similar enums in my shellcmd project, so you might encounter same problem)
no, devel is wrong, it is a regression. and pure should be deprecated.
Filed an issue, if you are interested https://github.com/nim-lang/Nim/issues/23579
its complicated. it only works on stable because of the order of the declaration of your enums.
I see, I will make attention to this next time I overload enums
Thanks for the info !
compiling included test results in