It's worth mentioning that they're not called padLeft and padRight because that would be confusing for strings written from right to left (there's an Unicode code point that marks the text direction, U+200F).
Glad you're back. After an improved promise support, now Node has async/await too, which makes everything even sweeter (also, in Node 8.x the performance of promises improved dramatically - not as fast as Bluebird but getting there).
I don't get why so many developers struggled with the async nature of JavaScript, but I guess you're in good company after all.
> The return statement ends function execution
That's not correct in some edge cases. Consider the following:
function foo() {
try {
console.log("foo");
return 0;
} finally {
console.log("bar");
}
}
When executed, it will print both "foo" and "bar".
Also worth mentioning that a return statement inside the finally branch with override any previous one.
> The return statement ends function execution That's not correct in some edge cases. Consider the following: function foo() { try { console.log("foo"); return 0; } finally { console.log("bar"); } } When executed, it will print both "foo" and "bar". Also worth mentioning that a return statement inside the finally branch with override any previous one.