Ad
  • Custom User Avatar

    The go version has random tests with values that overflow the int type.

  • Default User Avatar

    hey, I tried to compile this in c and the tests worked until the random ones where it got a error code 6. i was allocating the array with calloc and the stderr said something with free(): invalid next size (fast), you sure you free it in the right way? because from what i read err 6 can mean a heap overflow

  • Custom User Avatar

    Scala: assertion messages are unhelpful:

    DeadFishTest
    DeadFish.parse should work with example tests
    Test Passed
    Completed in 23ms
    DeadFish.parse should work with fixed tests
    Test Failed
    c (of class java.lang.Character)
    Stack Trace
    Completed in 4ms
    DeadFish.parse should work with random tests
    Test Failed
    O (of class java.lang.Character)
    Stack Trace
    Completed in 28ms
    

    I fear tests can be suject to overflow like other languages.

  • Custom User Avatar

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

  • Custom User Avatar

    CS: no basic tests and only 7 random tests.

  • Custom User Avatar

    I don't get it why my solution do not pass random test...
    This kata is too easy for 6 kyu

  • Custom User Avatar

    In JavaScript, which is overall more efficient? Using IFs statements, Swith-Case, or K-V pair object with anonymous function? I have seen people using IFs- S-C and my self using K-V objects(something I picked from C# unfortunately).

  • Default User Avatar

    Not sure if this is just me but rust is missing the random test cases and is erroring out when attempting.

  • Default User Avatar
  • Custom User Avatar

    Tests need to be revised in several languages. With a random string of length 10, a possible input would be "iissssssso", which should return [340282366920938463463374607431768211456], with a 39 digits number. []int in Go is unable to hold this, but random tests generate strings of length comprised between 20 and 40. Python and Ruby are ok since they have integers of arbitrary size. I don't understand how tests are made in Haskell, but the output should be [Integer] and not [Int]. COBOL, Rust, Groovy and JS have tests correctly adjusted. C has no random tests (there's an issue already opened about that). Typescript has strings up to 11 characters, which I think may generate overflow (?). Other languages need to be checked. Actually, tests should be rewritten for languages having big integers and use them.

  • Default User Avatar

    VB translation kumited. Please review and approve. Thanks, suic

  • Custom User Avatar

    Pretty nice kata, but if you make a state about invalid charcters you should make a test for it, encurageing those who make this kata to handle such outcome.

  • Default User Avatar

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