No random tests.
I spent hours on this and finaly realized in my sql noobness that the data type was not string but inet.... suddenly everything changed.
great challenge, if you wanted to be kinder to those just learning sql you could point out inet in the description somewhere.
I tried to use both the sorted array and the single-link list, but there is still a timeout on the last test. What else can i try to do?
Thank you, fixed (and changed tests :) )
So, in what way is it a spoiler? It seems more like an unnecessary gotcha. A less generous interepretation is that hiding that detail is punishment for those who do not write a prematurely optimized solution.
If you mean the asymptotics of the algorithm, then this information will be a spoiler
Performance requirements are not mentioned anywhere.
The number of tests is not a piece of information which should be hidden...
The number of tests is spoiler information?
just use test.expect(isCorrect, "meaningful error message here") instead of assert
test.expect(isCorrect, "meaningful error message here")
Different solutions can output strongly connected components in different sequences, so I need to iteratively check strongly connected components for occurrence in the response. I haven't decided to use sorting for tests yet, because it will take a long time. If you know a way to do it better using the framework, I will be happy to find out
Write tests using the test framework instead of plain assert.