"In JS functions, the 'last' return wins", by Jake Archibald.

Over the years I've seen this enough that I expect the described behaviour, but I was missing an efficient place and context to hold that knowledge. It was just "that thing".

Except for a "return" silently replacing an uncaught error? I don't think I've encountered that before. Ha!

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!