if i only timeout on the hardest one should i keep trying to submit or should i try to think of a better solution?
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)
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?
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:
It's unnecessarily difficult to remember the names, because there's no consistency.
Why it should be camelCase? Don't say "js style guide". Just say why it should be?