All languages obey this rule as of now, closing

I don't mind translations, but I don't know TypeScript so I can't make sure it's good. I posted on Codewars's Discord. Maybe, someone can check it for me

Well, not really. In general, std::string::size_type is not guaranteed to be exactly the same thing as size_t, and size_t is not required to be 64 bit, and unsigned long long is not required to be neither 64 bit, nor equal to size_t.

It can be on some platforms, or on most platforms, but it's not universally true or guaranteed.

NaN is invalid JSON value.

no

Gotcha, (merge conflict), so here's a fork

coords has been changed to coord to match the kata. meanwhile, the test suite does not seem to work the same way as C++ in regards to isolating the struct the in pre-loaded section. regardless, it's not a class, and I can't see how a warrior could make any effect in cheating the kata because the expected value is calculated before the arguments are passed to the user. if you can demonstrate otherwise, please explain how, thank you!

See the two examples:

• One has strings composed by only aor A, the odd one has not.
• The other example, has some permutations of abc, the odd one, hasn't.

So, similar is having the same letters in any capitalization any number of times.

I'll ask on Discord for some guidance on how to solve the issue in the best way possible

This might be happening because of the quadrant descriptions. I copy pasted the new ones, check if the issue is resolved

Oh, whoops. Fixed

I have taken a point from each of you in updating this translation. Thanks for the feedback.

Enum is not that bad in general, but if used, I would propose it to be rather something like

enum quadrants { FIRST=1, SECOND, THIRD, FOURTH };

This can be arguably a nicer design that just int. The quadrants can be argued to be named rather than numbered, and enums quite nicely model a small set of names.