Thank you everyone for criticism and comments, exactly kind of feedback (maybe not its contents) I wanted. Didn't expect junk I write (documentation, too) to be so incomprehensible. Except "key named 'value' causing confusion" (too much, no?), looks like I deserved it.

haukex, thank you for intention to suggest better algorithm or data structure -- I deliberately described it (failed to communicate though) as something abstract, it's really not worth anyone's effort.

P.S. As to benchmarking, you all are right again: loop with simple push to new array, of either element or its expansion, is faster than all of the above

In reply to Re^2: To splice or not to splice? What implementation is more readable, efficient, etc.? by vr
in thread To splice or not to splice? What implementation is more readable, efficient, etc.? by vr

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.