> On 16 Jan 2021, at 00:27, Parrot Raiser <1parr...@gmail.com> wrote:
> I'm setting up a new machine, and I don't want to install something
> I'm going to have to update in a week.
In about a week, we will have a new Rakudo compiler release. I think the
Rakudo* people will wait for that. So I w
Patches welcome!
Fact is: the JVM support group is very small. If you feel that this is
important, the best way to get what you want to see in Java support, is to work
on it.
> On 18 Jul 2019, at 05:53, Darren Duncan wrote:
>
> On 2019-07-17 2:18 p.m., Aleks-Daniel Jakimenko-Aleksejev wrote:
Fixed for Bag/BagHash with https://github.com/rakudo/rakudo/commit/fe38bdba62
Fixed for Mix/MixHash with https://github.com/rakudo/rakudo/commit/bcc8054a4d
> On 13 Jan 2019, at 22:03, Elizabeth Mattijsen via RT
> wrote:
>
> Fixed for Set/SetHash with https://github.com/rakudo/r
Fixed for Bag/BagHash with https://github.com/rakudo/rakudo/commit/fe38bdba62
Fixed for Mix/MixHash with https://github.com/rakudo/rakudo/commit/bcc8054a4d
> On 13 Jan 2019, at 22:03, Elizabeth Mattijsen via RT
> wrote:
>
> Fixed for Set/SetHash with https://github.com/rakudo/r
Fixed for Set/SetHash with https://github.com/rakudo/rakudo/commit/4bb5c33c72
> On 10 Jan 2019, at 18:22, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 (via RT)
> wrote:
>
> # New Ticket Created by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
> # Please include the string: [perl #133762]
> # in the subject line of all future correspondence about t
Fixed for Set/SetHash with https://github.com/rakudo/rakudo/commit/4bb5c33c72
> On 10 Jan 2019, at 18:22, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 (via RT)
> wrote:
>
> # New Ticket Created by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
> # Please include the string: [perl #133762]
> # in the subject line of all future correspondence about t
FWIW, with:
http://modules.perl6.org/dist/Hash::Restricted:cpan:ELIZABETH
one can restrict access to a hash to a certain set of keys:
use Hash::Restricted;
my %h is restricted = a => 42, b => 666; # restrict to keys at initialization
my %h is restricted; # restrict to keys a, b, c
> On
FWIW, with:
http://modules.perl6.org/dist/Hash::Restricted:cpan:ELIZABETH
one can restrict access to a hash to a certain set of keys:
use Hash::Restricted;
my %h is restricted = a => 42, b => 666; # restrict to keys at initialization
my %h is restricted; # restrict to keys a, b, c
> On
The problem is actually caused by the error reporting:
https://github.com/rakudo/rakudo/blob/08b951c8f33cfc702c308e64efcb44f3ec725117/src/core/Exception.pm6#L2969
The only heuristic I’ve been able to find so far that the value of $ns{$_}
suddenly is no longer fully qualified if the namespace d
The problem is actually caused by the error reporting:
https://github.com/rakudo/rakudo/blob/08b951c8f33cfc702c308e64efcb44f3ec725117/src/core/Exception.pm6#L2969
The only heuristic I’ve been able to find so far that the value of $ns{$_}
suddenly is no longer fully qualified if the namespace d
Fixed with 344a64e987 , tests needed
> On 24 Mar 2018, at 15:01, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> FWIW bisectable points to (2017-06-25)
> https://github.com/rakudo/rakudo/commit/a2133dbc6a00d1f87bb0644c829591144381d736
>
> ( before that it was giving bag(a, b) or bag(b, a)
Fixed with 344a64e987 , tests needed
> On 24 Mar 2018, at 15:01, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> FWIW bisectable points to (2017-06-25)
> https://github.com/rakudo/rakudo/commit/a2133dbc6a00d1f87bb0644c829591144381d736
>
> ( before that it was giving bag(a, b) or bag(b, a)
yes, this can be rejected. Unfortunately I don’t do RT so someone else will
need to do that.
> On 13 Oct 2017, at 13:48, Aleks-Daniel Jakimenko-Aleksejev
> wrote:
>
> Oh. I guess this has to be rejected then.
>
> On Fri, Oct 13, 2017 at 2:46 PM, Elizabeth Mattijsen wrote
That does indeed look wrong to me, investigating
> On 23 Mar 2018, at 15:04, Nick Wellnhofer (via RT)
> wrote:
>
> # New Ticket Created by Nick Wellnhofer
> # Please include the string: [perl #133016]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl
That does indeed look wrong to me, investigating
> On 23 Mar 2018, at 15:04, Nick Wellnhofer (via RT)
> wrote:
>
> # New Ticket Created by Nick Wellnhofer
> # Please include the string: [perl #133016]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl
Fixed with https://github.com/rakudo/rakudo/commit/bdd8143e6f, tests needed
> On 1 Jul 2017, at 15:20, Jan-Olof Hendig (via RT)
> wrote:
>
> # New Ticket Created by Jan-Olof Hendig
> # Please include the string: [perl #131684]
> # in the subject line of all future correspondence about this i
Fixed with https://github.com/rakudo/rakudo/commit/bdd8143e6f, tests needed
> On 1 Jul 2017, at 15:20, Jan-Olof Hendig (via RT)
> wrote:
>
> # New Ticket Created by Jan-Olof Hendig
> # Please include the string: [perl #131684]
> # in the subject line of all future correspondence about this i
Agree, should be closed.
> On 1 Mar 2018, at 15:10, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> It seems like it is fixed properly now. See this discussion:
> https://irclog.perlgeek.de/perl6-dev/2018-03-01#i_15872426
>
> On 2017-10-22 08:28:20, c...@zoffix.com wrote:
>> On Tue, 26 Se
I propose we change all onlies in the core to multis after the release and see
how this breaks things / makes things slower.
> On 16 Feb 2018, at 14:17, Zoffix Znet via RT
> wrote:
>
> Spotted another case where there's impact: whether or not a routine is a
> multi can have large impact on us
I propose we change all onlies in the core to multis after the release and see
how this breaks things / makes things slower.
> On 16 Feb 2018, at 14:17, Zoffix Znet via RT
> wrote:
>
> Spotted another case where there's impact: whether or not a routine is a
> multi can have large impact on us
> On 13 Jan 2018, at 22:38, Curt Tilmes (via RT)
> wrote:
>
> # New Ticket Created by Curt Tilmes
> # Please include the string: [perl #132718]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132718 >
>
>
> m: sub foo(
> On 13 Jan 2018, at 22:38, Curt Tilmes (via RT)
> wrote:
>
> # New Ticket Created by Curt Tilmes
> # Please include the string: [perl #132718]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132718 >
>
>
> m: sub foo(
> On 8 Dec 2017, at 19:21, Zoffix Znet via RT
> wrote:
>
> On Fri, 08 Dec 2017 08:28:32 -0800, comdog wrote:
>> This comes from an answer to a Perl 6 question on Stackoverflow that
>> showed a different bug:
>>
>>https://stackoverflow.com/q/45527881/2766176
>>
>> With put() it does not an
> On 8 Dec 2017, at 19:21, Zoffix Znet via RT
> wrote:
>
> On Fri, 08 Dec 2017 08:28:32 -0800, comdog wrote:
>> This comes from an answer to a Perl 6 question on Stackoverflow that
>> showed a different bug:
>>
>>https://stackoverflow.com/q/45527881/2766176
>>
>> With put() it does not an
Properly fixed with e5b49ce , tests needed for container type / default value
of auto-defined
variables.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-06-13 05:48:13, ronaldxs wrote:
>> From irc
>>
>> ht
Properly fixed with e5b49ce , tests needed for container type / default value
of auto-defined
variables.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-06-13 05:48:13, ronaldxs wrote:
>> From irc
>>
>> ht
The problem with let/temp for this situation has been fixed with
752299767bac3c49 . And tests are needed for that.
However, the underlying issue is that the default value of container
descriptors created automatically with “no strict” are Mu rather than Any.
This will need some deeper research
The problem with let/temp for this situation has been fixed with
752299767bac3c49 . And tests are needed for that.
However, the underlying issue is that the default value of container
descriptors created automatically with “no strict” are Mu rather than Any.
This will need some deeper research
If you normally create a class, the entry in GLOBAL:: is decontainerized:
$ 6 'class Test {}; use nqp; dd nqp::iscont(GLOBAL::)’
0
However, if you just assign to a key in GLOBAL::, the result *is* containerized:
$ 6 'BEGIN GLOBAL:: = class { }; use nqp; dd nqp::iscont(GLOBAL::)’
1
So maybe you
If you normally create a class, the entry in GLOBAL:: is decontainerized:
$ 6 'class Test {}; use nqp; dd nqp::iscont(GLOBAL::)’
0
However, if you just assign to a key in GLOBAL::, the result *is* containerized:
$ 6 'BEGIN GLOBAL:: = class { }; use nqp; dd nqp::iscont(GLOBAL::)’
1
So maybe you
Fixed with c9699ab , tests needed. Please note that this currently breaks
tests 55-56 in S02-types/range.t which appear to be a little too specific for
their own good.
> On 3 Dec 2017, at 05:28, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Today (2017.11,HEAD(e5b660e)) it prints thi
Fixed with c9699ab , tests needed. Please note that this currently breaks
tests 55-56 in S02-types/range.t which appear to be a little too specific for
their own good.
> On 3 Dec 2017, at 05:28, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Today (2017.11,HEAD(e5b660e)) it prints thi
Can be golfed to “Block but True”. Problem also existed for “Code but True”.
Fixed with e31a414 . Tests needed.
> On 3 Dec 2017, at 05:00, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-09-18 12:12:49, zef...@fysh.org wrote:
>> B
Can be golfed to “Block but True”. Problem also existed for “Code but True”.
Fixed with e31a414 . Tests needed.
> On 3 Dec 2017, at 05:00, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-09-18 12:12:49, zef...@fysh.org wrote:
>> B
Those are predecessors of the “react / whenever” syntax. I think that
therefore this ticket can be closed now.
> On 3 Dec 2017, at 04:58, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> what is `earliest`, `more` and `wait`?
>
> On 2015-06-06 16:40:28, r...@hoelz.ro wrote:
>> The attach
Those are predecessors of the “react / whenever” syntax. I think that
therefore this ticket can be closed now.
> On 3 Dec 2017, at 04:58, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> what is `earliest`, `more` and `wait`?
>
> On 2015-06-06 16:40:28, r...@hoelz.ro wrote:
>> The attach
Fixed with cd24b1c55d0c798c8fd776f , tests needed (also for OUTERS::)
> On 2 Dec 2017, at 13:06, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11, HEAD(5929887)) on MoarVM.
>
> Code:
> $OUTER::OUTER::OUTER::OUTER::True
>
> Result:
> ctxlexpad needs an MVMContex
> On 22 Nov 2017, at 19:31, Timo Paulssen via RT
> wrote:
> On Mon, 20 Nov 2017 12:13:47 -0800, ronaldxs wrote:
>> What about a native perl6 range loop? Couldn't there be some way for
>> Perl 6 / Rakudo to generate code competitive on a small range with the
>> "native-loop" example?
>>
>> perl6
> On 22 Nov 2017, at 19:31, Timo Paulssen via RT
> wrote:
> On Mon, 20 Nov 2017 12:13:47 -0800, ronaldxs wrote:
>> What about a native perl6 range loop? Couldn't there be some way for
>> Perl 6 / Rakudo to generate code competitive on a small range with the
>> "native-loop" example?
>>
>> perl6
Hmmm…. I guess this one does… good point! :-)
> On 18 Nov 2017, at 17:57, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Does it mean that this now needs tests?
>
> On 2017-10-30 06:42:25, elizabeth wrote:
>>> On 24 Oct 2017, at 12:56, Zoffix Znet via RT >> follo...@perl.org> wrote:
>>
Hmmm…. I guess this one does… good point! :-)
> On 18 Nov 2017, at 17:57, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Does it mean that this now needs tests?
>
> On 2017-10-30 06:42:25, elizabeth wrote:
>>> On 24 Oct 2017, at 12:56, Zoffix Znet via RT >> follo...@perl.org> wrote:
>>
Fixed with be9e19efd97755cfd , tests needed!
> On 10 Nov 2017, at 03:28, David Lowe wrote:
>
> This crash still occurs with rakudo 2017.10.
>
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation o
Fixed with be9e19efd97755cfd , tests needed!
> On 10 Nov 2017, at 03:28, David Lowe wrote:
>
> This crash still occurs with rakudo 2017.10.
>
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation o
f the lock-protected block, and the proxy gets sunk outside of
> it, thus causing concurrent access to the SetHash.
>
>
> On 14/11/17 16:03, Elizabeth Mattijsen wrote:
>> reducing the code to:
>>
>> use nqp;
>> my $lock = Lock.new;
>> my $hash := nqp::hash;
&
f the lock-protected block, and the proxy gets sunk outside of
> it, thus causing concurrent access to the SetHash.
>
>
> On 14/11/17 16:03, Elizabeth Mattijsen wrote:
>> reducing the code to:
>>
>> use nqp;
>> my $lock = Lock.new;
>> my $hash := nqp::hash;
&
reducing the code to:
use nqp;
my $lock = Lock.new;
my $hash := nqp::hash;
await ^16 .map: {
start {
for ^1000 {
$lock.protect: { nqp::bindkey($hash,"a",1) }
$lock.protect: { nqp::deletekey($hash,"a") }
}
}
}
does *not* make it crash. So it would appear that i
reducing the code to:
use nqp;
my $lock = Lock.new;
my $hash := nqp::hash;
await ^16 .map: {
start {
for ^1000 {
$lock.protect: { nqp::bindkey($hash,"a",1) }
$lock.protect: { nqp::deletekey($hash,"a") }
}
}
}
does *not* make it crash. So it would appear that i
This does not seem to appear if you add at least one key to the set before the
await. The segfault only appears to occur when adding a first or removing the
last key from the SetHash.
> On 10 Nov 2017, at 03:28, David Lowe wrote:
>
> This crash still occurs with rakudo 2017.10.
>
> On Thu, O
This does not seem to appear if you add at least one key to the set before the
await. The segfault only appears to occur when adding a first or removing the
last key from the SetHash.
> On 10 Nov 2017, at 03:28, David Lowe wrote:
>
> This crash still occurs with rakudo 2017.10.
>
> On Thu, O
Same, but with the new Telemetry module so you can see better what’s going on:
$ perl6 -MTelemetry -e 'for (1, 10, 100, 1_000, 10_000, 100_000) -> $limit {
snap; my $x; my $y = "x" x 100; $x ~= $y for 1..$limit }'
Telemetry Report of Process #79213 (2017-11-10T16:24:00Z)
Number of Snapshots: 7
N
Same, but with the new Telemetry module so you can see better what’s going on:
$ perl6 -MTelemetry -e 'for (1, 10, 100, 1_000, 10_000, 100_000) -> $limit {
snap; my $x; my $y = "x" x 100; $x ~= $y for 1..$limit }'
Telemetry Report of Process #79213 (2017-11-10T16:24:00Z)
Number of Snapshots: 7
N
Fixed with bdc73563f484325cc544 , tests were already added, can be closed.
> On 6 Aug 2017, at 17:13, Joshua (via RT) wrote:
>
> # New Ticket Created by Joshua
> # Please include the string: [perl #131846]
> # in the subject line of all future correspondence about this issue.
> # https://rt.
Fixed with bdc73563f484325cc544 , tests were already added, can be closed.
> On 6 Aug 2017, at 17:13, Joshua (via RT) wrote:
>
> # New Ticket Created by Joshua
> # Please include the string: [perl #131846]
> # in the subject line of all future correspondence about this issue.
> # https://rt.
A —ll-exception stacktrace would be useful in such a case :-)
> On 30 Oct 2017, at 15:24, Tom Browder (via RT)
> wrote:
>
> # New Ticket Created by Tom Browder
> # Please include the string: [perl #132377]
> # in the subject line of all future correspondence about this issue.
> # https://rt
A —ll-exception stacktrace would be useful in such a case :-)
> On 30 Oct 2017, at 15:24, Tom Browder (via RT)
> wrote:
>
> # New Ticket Created by Tom Browder
> # Please include the string: [perl #132377]
> # in the subject line of all future correspondence about this issue.
> # https://rt
Fixed with b6a4d5b20451c5c8a, this now DWIM, tests needed.
Error message being too long, fixed with 497e0582e6c64ccc04b2e9 .
> On 23 Oct 2017, at 14:28, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132353]
> # in the subject
Fixed with b6a4d5b20451c5c8a, this now DWIM, tests needed.
Error message being too long, fixed with 497e0582e6c64ccc04b2e9 .
> On 23 Oct 2017, at 14:28, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132353]
> # in the subject
> On 24 Oct 2017, at 12:56, Zoffix Znet via RT
> wrote:
> On Mon, 23 Oct 2017 09:12:58 -0700, sml...@gmail.com wrote:
>> On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote:
>> The "solution", IMO, would not be to make your quoted example work (by
>> adding further special cases to the retu
> On 24 Oct 2017, at 12:56, Zoffix Znet via RT
> wrote:
> On Mon, 23 Oct 2017 09:12:58 -0700, sml...@gmail.com wrote:
>> On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote:
>> The "solution", IMO, would not be to make your quoted example work (by
>> adding further special cases to the retu
Which goes back to the behaviour of nqp::unbox_n():
$ 6 'use nqp; say nqp::unbox_n(1e0); say nqp::unbox_n(1e0 + 4e-15)'
1
1
> On 21 Oct 2017, at 11:30, Elizabeth Mattijsen wrote:
>
> The problem is that both these values have the same .WHICH:
>
> $ 6 'say 1e0.
The problem is that both these values have the same .WHICH:
$ 6 'say 1e0.WHICH; say (1e0 + 4e-15).WHICH'
Num|1
Num|1
Nothing to do with Sets/Bags/Mixes/object hashes.
> On 20 Oct 2017, at 17:02, Victor ADAM (via RT)
> wrote:
>
> # New Ticket Created by Victor ADAM
> # Please include the str
Fixed with 8a88d14905248526415 , unfudged tests, can be closed now.
> On 15 Oct 2017, at 08:54, Zoffix Znet via RT
> wrote:
>
> On Sat, 13 May 2017 01:24:28 -0700, elizabeth wrote:
>> All issues appear to be fixed with
>> https://github.com/rakudo/rakudo/commit/407bce1dc2 .
>> Tests are needed,
Fixed with 8a88d14905248526415 , unfudged tests, can be closed now.
> On 15 Oct 2017, at 08:54, Zoffix Znet via RT
> wrote:
>
> On Sat, 13 May 2017 01:24:28 -0700, elizabeth wrote:
>> All issues appear to be fixed with
>> https://github.com/rakudo/rakudo/commit/407bce1dc2 .
>> Tests are needed,
> On 13 Oct 2017, at 07:52, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132283]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Disp
> On 13 Oct 2017, at 07:52, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132283]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Disp
> On 13 Oct 2017, at 07:37, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132281]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
Fixed with 975fcf6cfd8089bfc237 , tests needed
> On 13 Oct 2017, at 07:01, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132279]
> # in the subject line of all future correspondence about
Fixed with 975fcf6cfd8089bfc237 , tests needed
> On 13 Oct 2017, at 07:01, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132279]
> # in the subject line of all future correspondence about
Fixed with dd943eded83edb3753 , tests needed.
> On 7 Oct 2017, at 15:52, (via RT) wrote:
>
> # New Ticket Created by
> # Please include the string: [perl #132236]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132236 >
>
Fixed with dd943eded83edb3753 , tests needed.
> On 7 Oct 2017, at 15:52, (via RT) wrote:
>
> # New Ticket Created by
> # Please include the string: [perl #132236]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132236 >
>
> On 9 Oct 2017, at 10:38, jn...@jnthn.net via RT
> wrote:
>
> On Sun, 08 Oct 2017 19:13:34 -0700, ipatrol6...@yahoo.com wrote:
>> As per a discussion on the IRC channel, I am requesting that a
>> regression bug be filed regarding the incorrect handling of variables
>> referenced to packages by
> On 9 Oct 2017, at 10:38, jn...@jnthn.net via RT
> wrote:
>
> On Sun, 08 Oct 2017 19:13:34 -0700, ipatrol6...@yahoo.com wrote:
>> As per a discussion on the IRC channel, I am requesting that a
>> regression bug be filed regarding the incorrect handling of variables
>> referenced to packages by
Fixed with 56eef6967b54b16c , tests needed
> On 9 Oct 2017, at 06:38, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132249]
> # in the subject line of all future correspondence about this
Fixed with 12fcece494e12b , tests needed
> On 8 Oct 2017, at 13:18, Peter du Marchie van Voorthuysen (via RT)
> wrote:
>
> # New Ticket Created by Peter du Marchie van Voorthuysen
> # Please include the string: [perl #132246]
> # in the subject line of all future correspondence about this is
Fixed with 12fcece494e12b , tests needed
> On 8 Oct 2017, at 13:18, Peter du Marchie van Voorthuysen (via RT)
> wrote:
>
> # New Ticket Created by Peter du Marchie van Voorthuysen
> # Please include the string: [perl #132246]
> # in the subject line of all future correspondence about this is
> On 25 Sep 2017, at 08:21, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132156]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
> On 25 Sep 2017, at 08:21, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132156]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
> On 18 Sep 2017, at 19:45, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132121]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132121 >
>
>
> Apparently i
> On 18 Sep 2017, at 19:45, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132121]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132121 >
>
>
> Apparently i
Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
> On 18 Sep 2017, at 14:51, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132117]
> # in the subject line of all future correspondence about this issue.
> # http
Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
> On 18 Sep 2017, at 14:51, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132117]
> # in the subject line of all future correspondence about this issue.
> # http
> On 18 Sep 2017, at 04:39, Brian S. Julin via RT
> wrote:
>
> On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote:
>> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017-
>> 09-17#i_15176823
>>
>> Basically, a lot of core constructs aren't workable with user-land
>> su
> On 18 Sep 2017, at 04:39, Brian S. Julin via RT
> wrote:
>
> On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote:
>> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017-
>> 09-17#i_15176823
>>
>> Basically, a lot of core constructs aren't workable with user-land
>> su
> On 17 Sep 2017, at 07:29, Sam S. (via RT)
> wrote:
>
> # New Ticket Created by Sam S.
> # Please include the string: [perl #132109]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132109 >
>
>
> When calling `.skip` on
> On 17 Sep 2017, at 07:29, Sam S. (via RT)
> wrote:
>
> # New Ticket Created by Sam S.
> # Please include the string: [perl #132109]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132109 >
>
>
> When calling `.skip` on
Fixed with 3c9cfdba88287e23e0ced8 (and further refined by later commits),
tests needed.
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
>
> On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
>> On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
>> perl6-bugs-follo
Fixed with 3c9cfdba88287e23e0ced8 (and further refined by later commits),
tests needed.
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
>
> On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
>> On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
>> perl6-bugs-follo
> On 6 Sep 2017, at 22:46, J . David Lowe (via RT)
> wrote:
>
> # New Ticket Created by J . David Lowe
> # Please include the string: [perl #132042]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132042 >
>
>
> This sh
> On 6 Sep 2017, at 22:46, J . David Lowe (via RT)
> wrote:
>
> # New Ticket Created by J . David Lowe
> # Please include the string: [perl #132042]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132042 >
>
>
> This sh
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
> To recap the IRC discussion yesterday: no, we haven't had this so far (except
> for stdout/stderr), and have gotten away with it due to the lack of output
> buffering. At present, we can either choose between:
>
> 1) Start keeping a
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
> To recap the IRC discussion yesterday: no, we haven't had this so far (except
> for stdout/stderr), and have gotten away with it due to the lack of output
> buffering. At present, we can either choose between:
>
> 1) Start keeping a
FWIW, I couldn’t get this to fail on my MBP *while* running make spectest with
TEST_JOBS=8
Perhaps this is OS / CPU / compiler dependent?
> On 5 Sep 2017, at 09:17, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Oh. A crude way to reproduce it is:
>
> while :; do clear; PERL6LIB=lib ./
FWIW, I couldn’t get this to fail on my MBP *while* running make spectest with
TEST_JOBS=8
Perhaps this is OS / CPU / compiler dependent?
> On 5 Sep 2017, at 09:17, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Oh. A crude way to reproduce it is:
>
> while :; do clear; PERL6LIB=lib ./
Fixed with 51709e01c0788c466af , tests needed.
> On 31 Aug 2017, at 22:05, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132006]
> # in the subject line of all future correspondence about
Fixed with 51709e01c0788c466af , tests needed.
> On 31 Aug 2017, at 22:05, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #132006]
> # in the subject line of all future correspondence about
Fixed with a5014fd0855545cc083b3590 , tests needed.
> On 26 Aug 2017, at 13:10, Sam S. (via RT)
> wrote:
>
> # New Ticket Created by Sam S.
> # Please include the string: [perl #131962]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
Fixed with a5014fd0855545cc083b3590 , tests needed.
> On 26 Aug 2017, at 13:10, Sam S. (via RT)
> wrote:
>
> # New Ticket Created by Sam S.
> # Please include the string: [perl #131962]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
Fixed with 6cec6b7218650aff1780a4dd , tests needed
> On 26 Aug 2017, at 10:35, Sam S. via RT wrote:
>
> Shorter test-case:
>
>➜ say :{ a => 1, b => 2 }.FLATTENABLE_HASH;
>{Str|a => a => 1, Str|b => b => 2}
>
> Compare to a normal Hash which works fine:
>
>➜ say { a => 1, b => 2
Fixed with 6cec6b7218650aff1780a4dd , tests needed
> On 26 Aug 2017, at 10:35, Sam S. via RT wrote:
>
> Shorter test-case:
>
>➜ say :{ a => 1, b => 2 }.FLATTENABLE_HASH;
>{Str|a => a => 1, Str|b => b => 2}
>
> Compare to a normal Hash which works fine:
>
>➜ say { a => 1, b => 2
> On 17 Aug 2017, at 18:11, Zoffix Znet via RT
> wrote:
>
> On Thu, 17 Aug 2017 08:50:48 -0700, alex.jakime...@gmail.com wrote:
>> See this...
>
> See also timotimo++'s comment that TimToady cleared a revert if there were
> fallout:
> raschipi, gfldex, timtoady already said he'd retract the
1 - 100 of 603 matches
Mail list logo
