Some programmers that grew up with manual memory management e.g. C will swear against returning anywhere but the end of the method, in order to ensure allocated memory is freed (but they often continue to use that rule in managed memory languages, because they don't actually know why the rule existed in the first place). You'll sometimes see this pattern as:
var ret = something
... code that assigns (and sometimes reads!) ret in one ore more places ...
return ret
IMO, this is ugly AF and hard to follow.