Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
When trying to run a full test suite I keep getting "DeprecationWarning: Sampling from a set deprecated". I'm not even using any sets in my solution, only lists and a dictionary.
There's no failing testcase because your solution apparently returns a correct answer for all test cases. It just makes tests run too long, and they are force-stopped.
I am not sure what you mean by "print and flush", but it will help you if it would make your solution faster, yes. And will not help you if not :)
Well this is strange. For me, it was not only posible to check for invalid paths of "C" type, but also the site did not seem to intentionally slow down anything for me. Interesting. At some point, the site apparently went malicious.
I find it near impossible to check for invalid paths of the "C" type. One thing i tried to do is to document the coordinates of EVERY point I visit (not just corners), but it takes a while to process. Also, it looks like this website intentionally slows things down. Even the bruteforce solution runs pretty fast on my system, but here it times out after just 1 test.
But there's no test case presented that illustrates an issue. Would a print and flush help with this harness?
simple answer is your solution is not efficient enough for the more stringent tests
Can someone help me understand why all my tests pass but the harness times out?
Going for 2000 was a good idea, my brute-force solutions in Java didn't work :'D
Amazing kata, thank you very much!
"Performance" tag doesn't seem appropriate here IMO, and should be removed.
Thank you, @hobovsky. Approved 🖖
I added a Python fork which updates tests to use proper
@itdecorators. Please review.
Apparently fixed now.
Should be fixed in fork by @hobovsky
I like this one. As long as you know refering to a capture group in regex (and now I learnt something new - thanks) it's really easy to read. Nice one!
Loading more items...