JavaScript semicolon insertion: a silent logic-killer

Think you can start a new line after `return`? Cute. JavaScript's "helpful" semicolon insertion will stab you in the back. `return\n{ user: 'Gabo' }` becomes `return;`. Your function now silently returns `undefined`. The object vanishes. Is this a clever rule for cleaner code, or a silent logic-killer that semicolons exist to prevent? #GaboTips #JavaScript

To view or add a comment, sign in

Explore content categories