Earn extra honor and gain new allies!
Honor is earned for each new codewarrior who joins.
Learn more
  • This comment is hidden because it contains spoiler information about the solution

  • if n > 9, I suppose this doesn't work?

  • This comment is hidden because it contains spoiler information about the solution

  • I like this generalization! I don't think my solution is totally optimized, but it squeaked by in about 10 seconds. Probably didn't find the exact approach you were looking for.

  • This code made me smile, Clever one.☻(Actually, I'm really new to rust.)

  • ok. Sounds like it's a non issue, then (tho, that makes this 4 kyu pretty cheap)

  • https://www.codewars.com/kata/reviews/5d6a9e48b5ed5900016675b5/groups/5d6aee91476ab3000132db2c
    The solution runs 9300--9800 ms in Rust, which is the original language, so I suppose it's valid.

  • why did you use python 2.7 (deprecated soon) while the trainer is in py3 by default? => I checked using py3. That's the difference.

    whatever we finally do about this issue, the language verison ill have to be restricted (but I don't see a restriction to py2 as a good idea, even if that could solve the problem)

  • I don't understand you, since I ran my solution and it passed the test, but your time outed. So I changed everything back.

  • I answer here to your other message because it 's this issue that is related to that:

    I cannot edit the kata myself (no issue opened for long enough).

    The point is not to push the performances to the limit, but just to keep consistency between the description and the requirements. Without this, the kata becomes quite simpler. Too much simple imo, in python, because of "you know what".

    I have found parameters, at which my solution x2 takes 10.5 seconds to complete, and your times out.

    errr... afaik, that's the opposite, for now: yours (original) x2 still times out, while mine + yours still passes the tests.

    Note: you deactivated the "big numbers" batch of tests. That's not a good idea at all. It's one of the main point of the kata!

  • .

  • Ok, I understand your point. I have found parameters, at which my solution x2 takes 10.5 seconds to complete, and your times out.

  • This comment is hidden because it contains spoiler information about the solution

  • I saw you changed the internal solution but you used the wrong one. This is the one that shouldn't pass. ;)

    note: make the value of n less variable, in the random tests => randint(40000,50000) for example, then find a decent number of tandom tests so that the problematic solution is timing out.

    Note : still the other issue to tackle. ;)

  • I'm currently trying to tweak the test suite: your algo cannot beat the other improper one, apparently. I strongly suggest to replace all the same the reference solution and make JS approach invalid, since otherwise there is no way (apprently) to forbid the improper approach.

  • Loading more items...