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.
Are there any solutions that are faster than O(n^2), where n is the number of points given?
perf constraints are not prohibiting slower solutions to pass, such as mine
Does this answer your question?
Closing now.
Its a better solution than mine actually, and I am sure it should be faster than mine but Idk when I tested both, mine was faster by 200ms when I used next_prime function from gympy2 library and I generate primes for each given name and I didn't store any primes
Also complete lack of specification regarding expected time complexity etc.
all languages now have random tests
Is it just me or is this test now missing from Python?
3 years later, and because of ranking inflation, this (in my eyes) would be a solid 6 kyu puzzle right now.
Quite nice! My main hesitation is forward compatibility though. If the framework ever gets fixed, this will probably break. It also feels better to keep it visible in the tests so solvers can know what happens and wait for the framework to get fixed. Until it does, the current setup works for me.
OK.
Except you could pass the hardcoded tests with a wrong solution (we managed to).
That was the entire reason we switched it, easiest way to get an assertion of every step of that test was to use the refsol rather than generating all the test cases.
Why would anyone touch the refsol? I don't think we should design for people who put pva on their weetabix.
Also I'm more than happy to replace the refsol in the tests with another one, ours is implemented suitably differently for example.
That was already possible before, and honestly the chance of a regression major enough to break this making both into a mainline CPython release and then onto CW is effectively zero.
The chances of that literally only breaking this are also zero, so it's whatever. Would be caught by testing against the JS version after we see half the kata on the site explode directly after an update.
done
Fork approved. Test data still needs to be grouped better in sample tests though.
Loading more items...