Cool to know these operators do stuff in JS.

Can u pls explain

Boring

snap !

bruh

I know the difference: your solution will make both branches execute if func1() returns something not truth-ish!

I also guess the instruction was not clear enough

Correct is never best practice to return a stack allocated variable.

This will fix it, that is unless you are threaded - as this isn't thread safe.
static int newArray[length];

Allocating 500 bytes of memory and hoping for the best is not a good idea. As a buffer overflow will crash the code.
If you don't know how much memory you'll need you should realloc as you go, only returning as much as required and no more.

I too struggled with this until I read the discourse chats. Look for highest 5-digit "string fragment". Think "sliding window" over the string.

Test case exploit. This is not what is expected.

I'm exploiting a defecting in your testing to pass this. I suggest you improve the test harness.

Ok, I got it now. I was awear of the stack variables, was a little confused about the moment the memory is set to "writable". I see now my problem. Thank you for pointing it out! Have a great day/night!

Yep my bad its in the Data/BSS Section. However my point is that using static will make it persist beyond the scope of the function call.