return True if <condition> else False

==>

return <condition>

You're welcome, glad to help.

The ListBuilder was not putting things in the correct order which made the list became undefined -> undefined -> .... This has been fixed, thanks to your solution.

Thank you!
Took a while to come to an approach like that.

well done. I think this is the first I've seen with this approach in O(n) time

Nice!! Thanks to you!

Hi, Quark Fox!

Have a look at the example (0, 30, 0, 30) once again:

1. rotating the dial clockwise (instruction step#2) from zero to 30 will take 90 degrees;
2. rotating the dial counter-clockwise (instruction step#4) from 30 to zero will take another 90 degrees;
3. then again, rotating the dial clockwise (instruction step#5) from zero to 30 will take 90 degrees;

According to the instruction steps(#1, #3) you have a value of 360 times 2(#1) + 360(#3), which is 1080.
Now add this to 90*3 and you get 1350.

Hope that helps.

Translated test cases look nothing like the Java original (??)

Where is the validation function checking the user returned password?

Javascript translation:

https://www.codewars.com/kumite/64058635b2dd990031b7ece4?sel=64058635b2dd990031b7ece4

No, they actually don't move.
You can read the above line as It is the letter, that takes some amount (value) and moves it (i.e. adds or subtracts it) at a certain position.
So, the letters do stay put.

Yep, BigInt is fine, thank you.

Should BigInt be used in js solutions?

While having everything correct up to 57, mine fails at all the next bigger values.

Feels like the description lacks the line from wiki here:

Cards can be played onto a single shared stack, and players call "snap!" if two consecutive cards on this pile are identical.

It is not clearly specified how we should treat spaces. In some random tests, we got multiple adjacent spaces. To me it seems we should ignore any empty words we might get when splitting the text into words.

Hi, Anton!

Are you sure there is definitely a case with empty input?

Well, I guess there's none of them - all the inputs do contain certain values.

A possible cause to your illustration may be input mutating (i.e. you don't make a copy of an input array, but change that in place).