I think it does, could you perhaps help checking it? Thanks

my bad, is it ready right now?

Are we updating all C# kata's to C# 12 and this model of unit tests?

maybe the description should specify that the string only contains ASCII characters ? most solutions would be wrong for multibyte (Rust, C++) /UTF-16 strings (Java, JavaScript, C#...)

done

Thanks!

Sorry about the invoncenience. As you can see in the description now, you must make the hue to 0 even if it is 360. This will avoid possible confusion.

I also added the first test case in the random tests above as a fixed test.

Sorry for the issues!

Sorry, the 10k tests was only when I was testing it. I was a complete goofball and forgot to get rid of it.

As for the hue values, I'll start working on that now.

The reference solution is correct BTW. I brute forced it in https://www.codewars.com/kumite/670be7418cec2e9e1c4ea945

Thank you very much for all of these tips! I'll be sure to change this soon!

Should be fixed now!

Sorry that's just my stupidity in writing the description, can you tell it's my first kata? :)

Thank you for the feedback, clarification has been added to the description. The digits should just be truncated / rounded down.

One coercion won't change that time complexity much ( at worst, to O(log W), but that's still practically instantaneous ).

That would also not be the solution everyone is going to submit. If it's even correct.^{citation needed}

What would you do if it were a number? Convert it to a string and start slicing.

Might as well give us a number string.