Thank you, raiph, these are good ideas.

Using a junction is indeed a nice idea, and does improve readability, but I doubt there can be a performance boost in this specific case, because I can't see how the compiler or the VM could run this in parallel (or if it does, it would need to add a duplicate removal phase, it seems to me that this might be too much for a compiler optimization).

As for the * whatever pronoun, I should confess that I have been trying to use it from time to time, but am still uneasy with its syntax. Essentially, I haven't really figured out how the compiler can tell the difference between * as the multiply sign and * as the whatever pronoun, so that I have been using it so far with a try and error method, rather than with a true understanding of where and how this should work.

In reply to Re^3: Elegantly map fizz to buzz by Laurent_R
in thread Elegantly map fizz to buzz by oiskuu

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.