I have now 4 big p5p performance rants stored under ~/Documents/.
But I'm working on an official non-rant design draft https://gist.github.com/3740313
for the most common optimizing possibilities. Problem is that people are already implementing parts of it without knowing the internal problems behind.
So e.g. a function signature implementation makes no sense without lexicals const's ("is ro") being worked out before. Not talking about "is bind".
Nobody knows about perl6 and perl5i. Nobody is talking to them.
class/methods need to define the immutable/final semantics first. And I fear the decisions will be wrong. At least Stevan is a clever person not rushing things.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||