On Sat, 16 Sep 2017 22:29:57 -0700, sml...@gmail.com wrote:
> When calling `.skip` on a list which contains a `Slip` at the start, the
> resulting `Seq` behaves in some cases as if *all* elements from that
> `Slip` were skipped (instead of just the first one):
>
> say (, ).map(|*).skip.perl
On Sat, 16 Sep 2017 22:29:57 -0700, sml...@gmail.com wrote:
> When calling `.skip` on a list which contains a `Slip` at the start, the
> resulting `Seq` behaves in some cases as if *all* elements from that
> `Slip` were skipped (instead of just the first one):
>
> say (, ).map(|*).skip.perl
On Fri, 02 Jun 2017 18:58:22 -0700, c...@zoffix.com wrote:
> While chasing some other bugs, came across this one:
>
> m: Junction.new.BUILDALL: {}
> rakudo-moar ef9872: OUTPUT: «This type (Scalar) does not
> support elems in block at line 1»
>
> Not sure how much it matters in itself, but
On Mon, 29 May 2017 11:36:49 -0700, c...@zoffix.com wrote:
> On Mon, 29 May 2017 10:02:27 -0700, thunderg...@comcast.net wrote:
> > Using a cross meta operator on an empty list complains "This type
> > (Scalar) does not support elems".
> >
> > say (1,2).elems; say ().elems; say (1,2) X ();
>
I think this bug can be closed.
Here's my reasoning. For me, a major point with the auto-generated usage text
is that it helps the developer of the program see the importance of picking
good variable names. If a dev chooses to name them $integer1 and $integer2
(which are obviously horrible vari
On Sat, 30 Sep 2017 12:28:48 -0700, sml...@gmail.com wrote:
> Is `Junction.new` meant to be public API?
Don't see a reason why not.
> If not, do we still need a test for this?
If it weren't, all fixed bugs still need a test to cover them. If the test
should
not become part of the spec, it shoul
On Sat, 30 Sep 2017 12:28:48 -0700, sml...@gmail.com wrote:
> Is `Junction.new` meant to be public API?
Don't see a reason why not.
> If not, do we still need a test for this?
If it weren't, all fixed bugs still need a test to cover them. If the test
should
not become part of the spec, it shoul
I agree with Zoffix that this seems to be fine as is.
Generally speaking, IO operations that logically require an existing path will
return a Failure if the path does not in fact exist:
Slurp its content? Failure.
Rename/move/copy it? Failure.
Check its size? Failure.
Check if it is of t
On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote:
> To the extent that you're basing your expectations on the fact that a Perl
> 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without
> blowing up), well, that's just a matter of having to unlearn Perl 5 (or
> other programming
On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote:
> To the extent that you're basing your expectations on the fact that a Perl
> 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without
> blowing up), well, that's just a matter of having to unlearn Perl 5 (or
> other programming
On Sat, 30 Sep 2017 13:13:31 -0700, c...@zoffix.com wrote:
> Don't see a reason why not.
Well, passing a 'type' string parameter to select between what is essentially
different object sub-types, seems internal-ish.
I can't think of anything else in the public Perl 6 API which does this; a more
# New Ticket Created by Ville Koskinen
# Please include the string: [perl #132183]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132183 >
I downloaded and installed the latest Windows x64 build of Rakudo
(http://rakudo.org/d
On Sat, 30 Sep 2017 13:47:22 -0700, allber...@gmail.com wrote:
> So I included at least one discussion in the ticket that was utterly
> pointless and left unread. At this point I'm just going to assume only
> half-exposing the underlying mechanism is considered a feature and I need
> to use a diffe
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132191]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132191 >
There is very little known about the problem. I'm creating this ticke
14 matches
Mail list logo
