On Sun, Sep 11, 2016 at 6:49 PM, Zoffix Znet via RT
wrote:
> On Sun Sep 11 15:29:45 2016, tbrowder wrote:
>> Uh, say "what?" :)
>
> I don't think that works as a justification. The put() is used much more
> frequently than printf(),
> so it makes sense to have it as a "\n"-adding alternative to p
On Sun Sep 11 13:48:04 2016, tbrowder wrote:
> Both routines need an alias (or adverb) so that a newline is
> automatically appended to the output. I would like to see something
> like:
>
> sprintfn
> printfn
>
> or
>
> sprintf-n
> printf-n
>
> or
>
> sprintf-nl
> printf-nl
-1 from me.
--
# New Ticket Created by
# Please include the string: [perl #129256]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129256 >
How to reproduce:
perl6 -e 'use NativeCall; CArray[uint8].new(())'
Fix (not tested):
--- a/li
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #129257]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129257 >
[14:31] m: "%%foo @@bar".say
[14:31] <+camelia> rakudo-moar 15532d: OUTPUT«===SORRY!=== E
On Mon Sep 12 07:33:33 2016, darek.cidlin...@atlas.cz wrote:
> 2) should the newline before the ... operator be forbidden,
> the error message could be clearer than a single asterisk.
Thanks for the report, but I think I'm going to close this without any changes.
What happens is your } wi
For others reading the ticket. I asked OP to submit the fix[^1] to get some
practice fixing Rakudo bugs, so this ticket is taken.
[1] http://irclog.perlgeek.de/perl6/2016-09-12#i_13194275
Thanks for the report!
Unfortunately the fix you provided is a no-op, because empty arrays are falsy,
so the check doesn't add anything extra.
The issue was the nextsame candidate was the one with the slurpy that called
the current candidate back again, resulting in an infiniloop.
The issue ha
# New Ticket Created by Darek Cidlinsky
# Please include the string: [perl #129255]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129255 >
If a newline precedes the infinite list operator and the "next item" sub is
given as
Yep,
Just confirmed here with all the original examples I gave, all good.
Now to remember where it was I had hacked round this :-\
On Wed, 2016-09-07 at 10:40 -0700, Zoffix Znet via RT wrote:
> This now appears to have been fixed by some of the recent async
> fixes.
>
> Tests now pass and have b
# New Ticket Created by Jan-Olof Hendig
# Please include the string: [perl #129258]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129258 >
# tested with
This is Rakudo version 2016.08.1-169-g15532db built on MoarVM version
2
They do indeed behave somewhat inconsistently when the position is too high.
Consistency, and the off by one error, returns when using -1 though.
dogbert@dogbert-VirtualBox ~/repos/doc $ perl6 -e 'say "1234".index("2", -1)'
Position in index out of range. Is: -1, should be in 0..4
in block at
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #129259]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129259 >
It is a known issue, but I figured a ticket is not going to hurt.
Co
Yep,
Just confirmed here with all the original examples I gave, all good.
Now to remember where it was I had hacked round this :-\
On Wed, 2016-09-07 at 10:40 -0700, Zoffix Znet via RT wrote:
> This now appears to have been fixed by some of the recent async
> fixes.
>
> Tests now pass and have b
Ostensibly Perl 6 is meant to be a language ready for the next hundred years.
As such, I am wondering where either Perl 6 or its implementations have
hard-coded limits based on current or projected hardware limitations, or where
they don't.
Examples of what I would like to know, do any limits
# New Ticket Created by "Brian S. Julin"
# Please include the string: [perl #129261]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129261 >
A class attribute accessed too early in the compilation process will get nilled
out
On Mon, Sep 12, 2016 at 11:40 PM, Brian S. Julin <
perl6-bugs-follo...@perl.org> wrote:
> $ perl6 -e 'class A { my $.bar = 42; }; class D { constant bar =
> A.bar.say; }; A.bar.say'
> (Any)
> (Any)
>
The first one is expected, as the bodies of class definitions run at
compile time but initializer
16 matches
Mail list logo
