Yes, that is the one. Let's see what solvers have to say whether these are dups or not.

This game has been done before on Codewars.

sexy!

ok

The first soldier in line adopts Stan's cadence of 1 after 1 step already.

Soldiers at the ends of the line are influenced only by their single neighbor and adopt that neigbor's cadence.

Thanks for sharing your reasoning, Kacarott. I understand the technical reasons for creating a new challenge, especially with drastic performance changes. However, I still believe that, whenever possible, we should aim to improve and update existing challenges, and encourage the community to update their votes and feedback. This would help us maintain a high standard of quality and foster a culture of continuous improvement.

I agree that the quality and accurate ranking of the challenge are most important. My concern was less about "free points" and more about recognizing the community's ongoing engagement. Perhaps we could explore better ways to notify users about significant updates and encourage them to revisit and re-evaluate challenges.
Ultimately, I hope we can find a balance that both ensures challenge quality and values community input.

It's disappointing that the moderators suggested creating a new challenge. It seems they opted for the simpler approach instead of trusting the community to revise their votes. While I understand that many users don’t update their votes, this issue should be tackled directly rather than taking the easy and ultimately incorrect route.

Bad idea, here is why ..

Creating a new kata to bypass negative votes on the original challenge was not a good approach. Instead, you should have revised and improved the initial challenge, then informed users about the changes so they could update their votes accordingly. By discarding the original and starting fresh, it seems you prioritized votes over the community’s input, assuming users wouldn’t adjust their votes after the improvements. Moreover, this approach overlooks rewarding those who solved the original version of the challenge.

woopz

ethenyne should have 2 H elements:

python:

5000 random tests...
ethen-1-yne: {'H': 2, 'C': 2} should equal {'C': 2}
ethen-1-yne: {'H': 2, 'C': 2} should equal {'C': 2}
ethenyne: {'H': 2, 'C': 2} should equal {'C': 2}
ethenyne: {'H': 2, 'C': 2} should equal {'C': 2}
eth-1-en-1-yne: {'H': 2, 'C': 2} should equal {'C': 2}
ethenyne: {'H': 2, 'C': 2} should equal {'C': 2}
ethenyne: {'H': 2, 'C': 2} should equal {'C': 2}

Actually, can en and yn even be on same bond position? Looks like you are having multiple bonds between same two atoms, which is very weird. These cases do not occur in javascript, and should also be stripped from other languages.

Nevermind, that alkyl is optional. I found one last 'issue' before completing the kata.

The description states that arsines (and equivalents) have an alkyl prefix; however it can also be an aromatic cycle prefix, as this example shows from random tests:

triphenylarsine

Another random test:

13-amido-9-butyl-13-chloro-6,6-difluoro-3-heptadecyl-8-imino-5,7,10,12-tetraiodo-2-pentadecyl-5,10,11,12-tetra[nonyl]phosphinotridecan-1-oate

However, the spec stipulates that the suffix pattern for ester is alkyl " " alkan position "oate".

I believe this is an invalid molecule according to your own specs.

EDIT: or is the alkyl part optional and this test case is alkan position "oate"?

I'm not asking for any enforcement here. Ideally, I'd like to see this section of the specification either removed altogether or rewritten as an "extra challenge" note. The phrase "Please use" is ambiguous—it's unclear whether the author intends to prohibit certain solutions or simply wants to guide us in a particular direction.

You could have asked a question on the dashboard regarding performance requirements and legit strategies to solving this problem. Also, those other kata's that DO require us to exploit language features are 6-5 kyu. Did you really think a 1 kyu kata has an expected solution with a simple one line exploit as you pulled off?

I was only able to pass half of the 1024 bit tests in time. I was pretty tired and frustrated, I figured it's unlikely I missed some big optimization with the current approach, and figured the solution needs to be entirely different.