in reply to Re^4: Unexpected behaviour with constant lists
in thread Unexpected behavior of '..' lists

There's a specific set of ops meant for the range operator.
In general, yes, but those aren't used at all in this optimization. The only compilation difference between for (1..4) { } and for (1,4) { } is the former sets OPf_STACKED on the enteriter op. </c>
t's much better than the longhand for(;;) which would be lots of more ops to dispatch.
Yes.