Follow
"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!
