Coding style, clarity, and lack of need are all good reasons to omit it; performance isn't.

Sure it is.Performance is just as good a reason to adopt a certain style , heck, its even a better reason.

Explicit return adds less than 1% clarity in 99% of situations; while implicit returns outperforms it 98% of the time. 

$ perl -MBenchmark=:all -e " cmpthese -3, { a=>sub{return int @_}, b=>
+sub{int@_},c=>sub{scalar@_},d=>sub{0+@_}} "
        Rate    a    d    b    c
a  5279994/s   -- -35% -52% -67%
d  8131795/s  54%   -- -26% -50%
b 10997789/s 108%  35%   -- -32%
c 16189364/s 207%  99%  47%   --

[download]

In reply to Re^9: The Most Essential Perl Development Tools Today (implicit return) by Anonymous Monk
in thread The Most Essential Perl Development Tools Today by Tommy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.