1.6 is already available now. In general, new versions should be enabled automatically when the author's solution passes the tests. When they are not, updating anything to rerun tests usually helps.

this doesn't parse floats correctly. it parses "3.1" as 1.3 and "3.14" as 0.53

absolutely this.
in fact, generating the random strings dominates execution time. I tried a fork where the random string is generated once and provides substring slices for each test but even that times out when generating a single 100,000,000 term string.

Edit: i've created a fork which can generate random testcases fast enough, but guess what? even more numpy

hi, mostly updating so compiles with nim 1.6, but fixed tests so they display on failure.

do plz reply with reason if rejecting, i'm literally only here to update nim kata to 1.6, let me know what i can do to make that process as easy for you as possible

cheers!

should leading whitespace be allowed?
c++ translation doesn't test for it.

lol - I didn't know that was the only requirement to approve. Guess my grind isn't too big, at least I can start approving yours. :)

looks great to me.
i guess i'll just need to grind out 4000 honour and come back to approve

Minor changed, since introducing the block, why not make the test "printError: the block? Makes it nice and clean and shows the intent of the block to include check().

translation published. i thought putting helper display functions in 'Preloaded' would work, but maybe it's not implemented for nim?

update to a) fix sample_tests and b) enable nim 1.6
working now since https://github.com/codewars/runner/issues/194#issuecomment-1193073551

After https://github.com/codewars/runner/issues/194#issuecomment-1193073551 this now works with Nim 1.6

However, 1.6 is still greyed out when training. It's not possible to submit a translation with no changes.

Of course, in this case i can probably fix the sample test issue and publish a fork, but in general, how can one enable new versions if no changes are necessary?

how about that?

Please display the random test inputs and expected results same as the Java original.

great point re: dotest function not giving good error messages.

question: will trivial forks that only enable nim 1.6 (e.g. s/random/rand/g) not be accepted?