As far as widespread full stack goes, it depends on what the aim of the code is. If you're collaborating, then no, as the program can be unreadable and leaving comments as insurance is too timeconsuming. In the end, we usually try to find a reasonable balance between using concise syntax and structure while the code is still easily readable to a third party. But when in comes to more specialized areas I don't have the experience to say so I guess it's possible.

thanks for showing this awesome functional approach

Love this use to spreading strings to arrays!

Only Safari browser actually supports tail optimization, so it is better to think that JS does not support it at all.

JS does support tail call optimization. This solution however is not tail recursive, so will eventually cause a stack overflow if n is sufficiently large.

JS does support tail call optimization. This solution however is not tail recursive, so will eventually cause a stack overflow if n is sufficiently large.

Thank you.
I'm not familiar enough with JS to confirm if this is good practice, in the sense that :

• does JS support tail optimization ?
• If so, does this particular construct allows it.

nice

Giving only examples with sorted input arrays, leaving their sortedness unspecified, and in the Submit tests coming up with unsorted input arrays feels dishonest.

This has not been addressed. At all.

Your random tests are still vulnerable to input modification.

This solution should not be valid.

Ehm .. how?

I'm not seeing it.

Yes, I refreshed.

Thanks! fixed it

sick!!

This.

Changing properties of input arguments will have the test process those modified inputs, because they're reused blindly.