Binding of the map routine internally now requires list elements to bind as
Pair, which improves the error message.
(The alternate approach of inserting a CATCH into the map closure could in
theory produce an even better message, but it appeared to slow things down more
than the Pair binding ap
# New Ticket Created by Wenzel Peppmeyer
# Please include the string: [perl #128915]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128915 >
my %multi-dim;
%multi-dim{1;2;3} = 42;
dd %multi-dim{1;2;3}
# OUTPUT«(42,)»
# expec
Some method calls were not properly sunk as a final statement in a loop.
Fix in 977797fa401856e5310155f13469b7e6ff5f620a
Test in bc8fa4fd8d449573eb6001b5f43f8890f65b9196
Attached is a straightforward implementation of the floating-point
printf conversions. I believe it to be correct. In addition to the
decimal %e, %f, and %g, I did the rather useful hexadecimal %a, thus
far entirely missing from Rakudo's sprintf.
I needed some supporting floating-point utilities
The only difference between “push” and “say” I can find, is that “push” is
marked “is nodal”
However, trying to replicate this outside of the setting, does work as expected:
$ 6 'class A { proto method a() is nodal { } }; say A.^can("a")[0] ~~ Callable
True
Looks like it is even deeper, at the
Will look at this as part of a Set/SetHash overhaul
> On 12 Aug 2016, at 05:19, Wenzel Peppmeyer (via RT)
> wrote:
>
> # New Ticket Created by Wenzel Peppmeyer
> # Please include the string: [perl #128903]
> # in the subject line of all future correspondence about this issue.
> # https://rt
Hmmm… the todo’d test for this now passes, but the problem still exists (apart
from the hanging). So I guess this is a Test Needs To Be Adapted case.
> On 10 Jul 2016, at 22:58, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #1285
Fixed with be7ce04 , tests needed
Turns out this was slightly more involved than just setting up a CATCH block,
as the CATCH block will only be seen either in the executing thread, or in the
.tap block of the signal handler.
So in the end, I decided to always start the code in a separate threa
# New Ticket Created by djgoku
# Please include the string: [perl #128904]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128904 >
I wanted to do (IRC Log of #perl6:
http://irclog.perlgeek.de/perl6/2016-08-12#i_13009688
# New Ticket Created by Zefram
# Please include the string: [perl #128914]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128914 >
> "9.998e0".EVAL - "9.998e0".Num
1.77635683940025e-15
Observe that the
# New Ticket Created by Zefram
# Please include the string: [perl #128913]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128913 >
> "9.9981e0".EVAL < "9.998e0".EVAL
True
Observe that the literal with
# New Ticket Created by Zefram
# Please include the string: [perl #128912]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128912 >
> (9.999e-5 * 2e0**66).Int * 5**8 - * 2**58
287369
> (9.99895e-5 * 2e0**66).In
Working on this now
> On 11 Aug 2016, at 20:35, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #128900]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=128900 >
13 matches
Mail list logo