My friend, we write solutions not tests. The TESTS round answers, not solutions. What are you talking about?

me to :')

Mine could've been a one-liner too but I stored (n*2-1) in a variable since it is called 2 times

I spent an hour on this and wrote 43 lines of code, but maybe just five. FIVE LINE, CARL!

• Updated to Rust 1.66
• Added assertion messages
• Added a fixed test that contains identical numbers

This is exactly the reason I enjoy codewars katas so much. Learn something knew every day.

:O I didn't know you could do that

I am not sure where Codewars rules say thay you need to be as fast as possible :)

i mean, codewars is sbout doing it as fast as possible, even if its extremely ugly

can't be!
———
"For I was conscious that I knew practically nothing..." | Plato

since no constraints for the arguments are given in the statement, add_binary(!0u64, !0u64) would cause overflow

the only thing I know is that I know nothing.

the kata needs clarification but I think if it meant to return "bye" and not "e" then it should also return "hi" if "hi" is the only argument. otherwise it's inconsistent. what if the arguments were ("hello", [1, "world", [2, 3]])? Should it return [1, "world", [2, 3]], [2, 3], or 3 ?

count_ones/popcount is a (somewhat) common CPU operation