Old kata syndrome, can't be changed as of now :-)

You're quite right. I used string too, before passing all tests. The reason, in my opinion, is that string catenation involves repetitive memory allocation 'coz a new string is created each time. But for byte slice, RAM is much more efficient, therefore faster.

I'm referring to the post by @pa-m, which is clearly an issue. Your mentioned post is about the Rust version. Just because it still hasn't been fixed, doesn't mean you should duplicate the issue.

You can comment on the existing one or upvote it. Even more effective method is to reply to the post that published the translation, which notifies the translator. Another option is to post about the issue on CW Discord server, and pinging the translator if they're available there.

This issue was already raised below

I did not want to start from 1089 because i felt that knowing it was the smallest was like cheating, so i thought of starting from 1 but the numbers from 1 to 11 can be excluded by basic calculations trough thinking so i just started from 12, hope i explained it well enough.

Use Console.WriteLine("*" + s + "*"); see where the * are. It's not "a".

Because it's not "a". Look for spaces (or something else) before or after it.

In the context of bitwise-operations flipping a bit is just that, setting it to 0 if it was 1 and to 1 if it was 0. Hint: note that indexes are 1-based in the kata.

Please:

• Say which language you are using
• Provide a clear example with input, output, logs