it was a bit weird for me at first cuz idk what a class means

Congrats!

7 January 2024 (180 lines)
This kata is great. I have devoted for this challenge about full 20 days.
My time is 10644.66ms. I know that it is too much, but .... so many attempts were done during these days.

.

I think that there's more solution based on another paper (or at least mine and monadius' is, which makes it two :) ). I am not sure why, is it more googleable, or what. I think I've seen the one you used but I found the other one easier to implement.

I thought my solution was super janky but once I got it working it was under 2.0s.

Did I just stumble upon a cracked algorithm in my research?

Reading through other solutions and there's fancy stuff going on I don't begin to understand... to MDN I go :)

Great Kata! Took me a long time, but I learned a lot.

Transltor's solution in Python takes 5-5.5s, while translator's solution in C++ takes 5-6 seconds. JS and Rust are faster: Rust goes slightly below 2s, and JS transltor's solution is poor and takes 8-10s, but there are submitted solutions which take below 3s.

Your solution is quite fast compared to other ones, runs mostly below 3s, what makes it quite similar to the rest.

Python does not seem to be any special outlier here, and solutions are not that distorted either: Python has fewer solutions but at the same time was published a year after JS translation, spent a lot of time in a freezer, and at the same time (for some reason) C++ and JS solutions are copied by cheaters much more often than Python ones.

Nice kata! What an adventure this was. I can't believe I solved it in the end! :D

I just found that if I simply return None, then for the tests which have a solution it would return like that. I think maybe the error msg should be changed so that it would not make us so confusing.

for some tests, I got "Solution is not a string" and "Test Passed" at the same time and for otehr tests it works normally. Can anyone tell me why this happened?

does this use threads? my statics are broken

Went off the deep end for a few days trying to optimize a method to manage the board's data. It sounded fast on paper but painfully slow in comparison to what just dawned on me a moment ago. Regardless, it ended up pretty much the same as everyone else's solution.

Pretty satisfying to see big boards getting solved in milliseconds instead of seconds per case before timing out.

Thank you for pointing it out.