Ok, maybe what it should return would be some sort of ReversedRange object?
I guess this could be considered a feature request, but, I'd like is for
(^5).reverse.reverse
and similar to be able to produce a Range.
-Original Message-
From: Moritz Lenz via RT
Sent: Friday, November 20,
On Nov 12, 2:21 pm, stefa...@cox.net (Stefan O'Rear) wrote:
On Thu, Nov 11, 2010 at 05:47:46PM -0800, Ben Goldberg wrote:
I would like to know, is perl6 going to have something like select
(with arguments created by fileno/vec), or something like IO::Select
(with which the user doesn't need
I would like to know, is perl6 going to have something like select
(with arguments created by fileno/vec), or something like IO::Select
(with which the user doesn't need to know about the implementation,
which happens to be done with fileno/vec/select), or only an event
loop.
I would recommend
On Oct 15, 9:57 am, markjr...@gmail.com (Mark J. Reed) wrote:
On Fri, Oct 15, 2010 at 7:42 AM, Leon Timmermans faw...@gmail.com wrote:
Continuations and fibers are incredibly useful and should be easy to
implement on parrot/rakudo but they aren't really concurrency. They're
a solution to a
On Oct 22, 6:41 pm, dam...@conway.org (Damian Conway) wrote:
Dave Whipp wrote:
When this issue has been raised in the past, the response has been that
junctions are not really intended to be useful outside of the narrow purpose
for which they were introduced.
Hmm. There are
I know that perl6 has / will have lazy strings, since (in
S32::Containers) the List role defines a cat method, which returns a
Cat object, which does the Str interface, but generates the string
lazily.
First, are Cat objects documented anywhere else?
Secondly, if a regular expression match is
Has there been any decision yet over what model(s) of threads perl6
will support?
Will they be POSIX-like? ithread-like? green-thread-like?
It is my hope that more than one model will be supported... something
that would allow the most lightweight threads possible to be used
where possible, and
