• if i only timeout on the hardest one should i keep trying to submit or should i try to think of a better solution?

  • Unspecified AssertionError.

    result of hardest test 1 - [ 1, 21, 22, 23, 24, 25 ]

    my results in test case was correct.

    somebody please explain what is happening here.

  • Ruby 3.0 should be enabled, see this to learn how to do it

    Please organize the structure of test fixture as following (although it has been mentioned in the attached link, I'm repeated here again)

    describe "<This message should describe the categories of test groups inside this block>" do
      it "<A short message describing this test group>" do
        expect(...).to eq(...) #Assertions
        #Or Test.assert_equals(user_response, reference_response)
      end
    end
    
  • time out is really confusing issue

  • this time out issue really irrelevant what's going on

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

  • console.log is POWER hah

  • The number of lines probably do not effect performance. Please check your algorithm again.

  • My code is just 1 line long and it still says execution timeout. Can somebody help?

  • Fixed

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

  • Because that's the standard. Have a look at the other katas on the site, or look at the names of in-built JavaScript functions:

    isInfinite, parseInt, lastIndexOf, copyWithin, toLocaleLowerCase, etcEtcEtc

    ...and yes, style guides: Google, jQuery, W3Schools

    To explain from the opposite direction, look at these in-built PHP functions:

    • htmlentities, html_entity_decode, strchr, str_pad, gettype, get_class, is_numeric, isset (inconsistent underscore usage)
    • strtolower, deg2rad, strtotime, ip2long (inconsistent use of 2/to)
    • file_get_contents, fwrite (inconsistent abbreviations)

    It's unnecessarily difficult to remember the names, because there's no consistency.

  • Really dude?

  • Why it should be camelCase? Don't say "js style guide". Just say why it should be?

  • Loading more items...