hi:) looks like you return same characters given in start
CLang:
Could someone explain this? What I misunderstood?
Failed lastSurvivors("zxyphjtvyiikdo") Actual characters: "zxyphjtvyjkdo" Expected characters: "adhloptvx"
Marking question as resolved as kata has since been solved 30+ times in C with no further issues, so everything seems to be OK with random tests in C.
Neither compiler has the duty of giving right or wrong values, that's up to the code. Yours gives erroneous values to the compiler.
Submitted
Expected
Examine your results for this test per each run
...so run the code several times and look at the error message for "That particular Fixed_Test" (the one that should return {61, 49}).
Fixed_Test
{61, 49}
This comment is hidden because it contains spoiler information about the solution
That particular test is a Fixed_Test, so it will run every single time you click ATTEMPT. Examine your results for this test per each run for a clue as to what's going on in your code.
ATTEMPT
No, it's unexpected.
simple ariphmetics :)
Loading collection data...
hi:) looks like you return same characters given in start
CLang:
Could someone explain this? What I misunderstood?
Failed lastSurvivors("zxyphjtvyiikdo") Actual characters: "zxyphjtvyjkdo" Expected characters: "adhloptvx"
Marking question as resolved as kata has since been solved 30+ times in C with no further issues, so everything seems to be OK with random tests in C.
Neither compiler has the duty of giving right or wrong values, that's up to the code. Yours gives erroneous values to the compiler.
Submitted
is what your code returned.Expected
is the correct answer for the current input....so run the code several times and look at the error message for "That particular
Fixed_Test
" (the one that should return{61, 49}
).This comment is hidden because it contains spoiler information about the solution
That particular test is a
Fixed_Test
, so it will run every single time you clickATTEMPT
. Examine your results for this test per each run for a clue as to what's going on in your code.This comment is hidden because it contains spoiler information about the solution
No, it's unexpected.
simple ariphmetics :)