allocation scheme is really nice ;-)

wmemset() is clever, but it abuses the fact that Codewars runs on Linux. On Windows wchar_t will be 16-bit, so the int would be set to 00 01 00 01 instead of 00 00 00 01

I presume that we can having null prototype means being on top of the inheritance chain, hence the correct answer for that case would be 0, same as for plain {}.

Added an example test case for showing that.

It doesn't solve the possible issue of having null prototype object passing into the function though: Then what should it return? Would this case even be tested in the first place?

Thanks, updated random test.

Thank you for your note.

Added a clarification for that issue:

So, every prototype actually inherits Object through inheritance chain (except for Object prototype itself, which has null prototype, and prototypes created with Object.create(null)).

Added random tests, please check.

Since every prototype is an object itself, simplest prototype's prototype will be Object, which means that it inherits prototype Object. So, every prototype actually inherits Object through inheritance chain.

This is false: Object.create(null) is a thing, and the prototype of Object is also not a prototype of Object. In fact this is so common console.log will print [Object: null prototype] for all of the above, and has legitimate use cases (e.g express request .body has a null prototype).

This would also mean the kata's premise is flawed, and needs to be revised.

@rowcased, https://www.youtube.com/watch?v=PgsvWeaqqW4

I'm no expert at English, but I don't think it's syntactically or logically correct to ask how many . So, one might otherwise pose the question as either, Which layer of inheritance are you on?, or maybe How many layers of inheritance have you reached?.

Thank you *dolayermroth

Thank you dolamroth, very cool

As a man of culture, you should name the kata "How many layers of inheritance are you on?"

Hi again,

• issue: Missing random tests.
• suggestion: you could not give the starting code (at all). Or just keep it the way it is right now. Up to you.

Cheers

Hi,

A kata should have more random tests than just one.

Did you already dive into the authoring documentation? If not, you should begin there, to get a clearer idea of what has chances to get approved or not.
https://docs.codewars.com/authoring/guidelines/kata

Cheers