Ad
  • Custom User Avatar

    Tests are severely lacking: only 2 threads are tested, so it is very easy for a basic deadlock checking to pass.

  • Custom User Avatar

    What is the expected handling if a thread tries to acquires a mutex it has already acquired?

  • Custom User Avatar

    Solutions like this should be patched.

  • Custom User Avatar

    If a method changes the internal object state, if you call this method both on the substitute and the original object, the resulting objects should continue to be "interchangeable" in the sense defined above. (See the String example below if you are not sure what I mean.)

    This is an absurd notion: if the original and the substitute object are supposed to be the same, then calling mutating methods on both objects should result in this being applied twice (and calling on either side should cause both to be mutated and remain the same). Otherwise they're different, and they cannot be considered the same object (as not every object supports .clone).

  • Custom User Avatar

    I swear I mean that in the nicest way possible. Generally not good to inherit from Hash, but this solution is super clever.

  • Custom User Avatar
  • Custom User Avatar

    Needs definition/description of "thread".
    Needs examples.

  • Custom User Avatar

    Hi,

    There's an issue with the Python (3) translation.

    Athough I am correctly raising the exception in the event of a deadlock, it seems the threads are never terminated in the tests (both example and full suite) so every test run ends with a timeout.

  • Custom User Avatar

    Aah that's clever. I have one question though:

    So if a condition is not met the first time a ternary statement is
    called, and there's recurssion on the false side, would it ever go
    through the true side again? (i.e. would it just keep going back to
    the recursive point, which is the false side in this case?).

  • Custom User Avatar

    Linear regression has been done (e.g https://www.codewars.com/kata/5515395b9cd40b2c3e00116c), so this kata is a duplicate.

  • Custom User Avatar

    wrong a/wrong b is terrible (and unacceptable) test feedback, so they should be changed. At least the expected and actual value should be shown, like in assert_equals.

  • Custom User Avatar

    I'd suggest requiring the solution to deal with a set of points such as this:

    [[1, 3],
    [1, 5],
    [1, -7],
    [1, 10]]
    

    …and to add correspondint tests.

  • Custom User Avatar

    Also, needs more tests.

  • Custom User Avatar

    Sample tests uses Object but BasicObject is used in the actual tests.

    They're completely different.

  • Custom User Avatar

    Test messages are very unhelpful.

  • Loading more items...