in the majority of languages with automated trash collection it’s strictly even worse from a technical perspective to prohibit several returns, therefore long as it’s refrained from doing poorly, there’s no maintenance/readability loss either.
for instance, if you have a series of loops trying to find some worth in several sources, and you discover it, simply return it instantly from the loop. it’s substantially faster to perform than actually every option you might compose as it takes less directions and less memory.
even crazier, this is really MORE maintainable in a lot of cases, and substantially less lines of code. if you do not return it instantly, the just other alternative is to keep it, break, and after that have extra conditional reasoning to avoid the subsequent loops since it’s currently been discovered (or you might browse them anyways losing a lot more time and memory).
where it can end up being a problem is systems with bad or no trash collection (taking a look at you PHP), or where the structure of the function is not semantically tidy, so the return declarations are all over the location.