no do not worry, there was nothing you could do, it's an old Codewars flaw, i had just not foreseen it would happen

should I have done something different?

well that reset the timer :facepalm:

approvable in 1 week ...

it's not really an "issue" but a mistake people are likely to make, and that makes one scratch their head for a moment. what caused it for me was that in prototype methods, this always has type object, even for primitives (they are "boxed"), i.e. :

String.prototype.f = function () { console.log(typeof this); };
''.f(); // 'object', not 'string'

and assert.deepEqual(new String('abc'), 'abc'); fails (as it should, imo). but once stringified by chai, they look identical

fork approved, issue fixed

fork

merge conflict

it'll be tough to fix since the stringification happens as one would expect, and I think deepEqual() failing is the right behavior. It was interesting to figure out what was happening too. I dont know what should be done here - a warning in the description ? a dedicated it() block with an helpful title ?

check the warnings generated by your code. also check this out:

unsigned a = 5;
int b = -1;
printf("%u is %s than %d\n", a, (a > b) ? "greater" : "less", b);

this is why you needed a cast.

i added random tests to JavaScript

done

approved

added to Ruby, C++

added + enabled Ruby 3.0 + RSpec assertions

fork for C