Here is what the first example would do without the new :injective flag, and why:

In general a map can aggregate multiple values per call to the transforming block, so accessing @result[7] would fill @result eagerly up to index 7, so the expected output looks something like this:

[0][1][2][3][4]13
[5][6][7]57
3
[download]

I seem to recall that TimToady actually said that map (and likewise for) do guarantee an order of execution, so even if the compiler can prove that the block passed to map will only ever return exactly one item, it will still process them in the way I described.

The :injective flag is a nice idea on your behalf, but since the array has to know how to evaluate itself (not just the map) that's a bigger change than just adding a flag to a builtin, it requires a different underlying List implementation.

Together with the other flags you propose I think that there are too many confusing options on how to process lists. If we do integrate them into the language, we'll see dozens of threads on perlmonks discussing the merits and drawbacks of the various flags when they are really just premature optimizations.

The current state of the specification also suggests that laziness is not strict, ie the map is actually allowed to process more than it has to, as long as it doesn't suck up infinite resources when trying to process an infinite list.

So my proposal is to use (lexically scoped) pragmas instead:

use List qw/strict-lazy/;
# now all list processing is haskell-like strictly lazy
# this is mostly good for testing laziness ;)

use List qw/parallel/;
# allow parallel processing of lazy lists, even when 
# when it's not that lazy. This is the default.
[download]

I think that all further attempts to control what happens under the hood are

• optimizations that the compiler should care about, not the programmer
• actually contra-productive, because it means we have to define the current semantics of laziness more precisely, thus taking the compilers the freedom to optimize
• not very perlish, in that we usually try not to expose what happens under the hood. It should just work, you know

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.