Ruby 3.0 should be enabled.
Seems the right solution. Even if tests are easier to pass now than before, performance requirements may still be tough given current runner.
Given the long-standing runner perf issue, what should we do for katas that have become impossible to pass? I could edit the kata to adjust its tests, but if the perf issue ever resolves, the katas may become too easy to pass.
Already reported issue below, closing this one.
Very frustrating if you get timeouts, although the identical solution has worked for others!! (python)
Python 3.6 should be enabled.
@pavloslav Right observation. To be super clear: entire solution is linear (only walking through input once and so on), except last step - sorting output.
people are always sorted at least in JS. Either it should be specified in the description or tests with unordered people should be added.
issue confirmed (the expected solution is linear)
issue confirmed: it's the runner perf problem. The tests need adjustement in python.
To be clear: THIS CODE TIMES OUT.
def find_gatecrashers(people, invitations):
It's the tests failing, not the code. Fix the tests.
How did you manage to build a linear solution here? Both collections are not sorted, and the result should be sorted. Sorting is minimum O(n*log(n)).
There's no clue for what numbers are in the list. There's only collection of party members (like [1, 100, 53435]) and collection of invitation (maybe not used at all).
can you clarify about my issue above??