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 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
> On 26 Feb 2017, at 07:06, Itsuki Toyota (via RT)
> wrote:
>
> # New Ticket Created by Itsuki Toyota
> # Please include the string: [perl #130863]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=130863 >
>
>
> See the
Fixed with 551b8a69e0a83e2c34 , tests needed
> On 1 May 2017, at 13:24, Jan-Olof Hendig (via RT)
> wrote:
>
> # New Ticket Created by Jan-Olof Hendig
> # Please include the string: [perl #131240]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/
Fixed for the .values case with c1bd844e2752799af8e and 0e0ac2fb8c51a82a0 .
But this needs a more thorough fix. To be forthcoming soon!
> On 1 May 2017, at 19:28, Elizabeth Mattijsen (via RT)
> wrote:
>
> # New Ticket Created by Elizabeth Mattijsen
> # Please include the
Fixed with 31be51284e70badd8ed , tests needed.
> On 8 May 2017, at 20:25, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #131272]
> # in the subject line of all future correspondence about t
Fixed for (elem) and (cont) with
https://github.com/rakudo/rakudo/commit/ba0581d75b .
Tests needed.
> On 12 May 2017, at 21:22, Zoffix Znet via RT
> wrote:
>
> On Fri, 12 May 2017 12:07:11 -0700, c...@tilmes.org wrote:
>> m: say 1 ∈ (Set) ?? 'present' !! 'not present';
>> rakudo-moar dc5eec: O
> On 13 May 2017, at 03:45, Brad Gilbert via RT
> wrote:
> On Fri, 12 May 2017 03:04:46 -0700, elizabeth wrote:
>> m: class A { has Int $.a is default(42) }; dd A.new.a
>> # expected to see 42 there, not Int, so feels like "is default" on
>> attrs isn't implemented?
>
> It does work if
All issues appear to be fixed with
https://github.com/rakudo/rakudo/commit/407bce1dc2 .
Tests are needed, also for the ⊇ and ⊉ and associated cases.
> On 12 May 2017, at 21:22, Zoffix Znet via RT
> wrote:
> On Fri, 12 May 2017 12:07:11 -0700, c...@tilmes.org wrote:
>> m: say 1 ∈ (Set) ?? 'prese
Argh. This is waiting for the refactor of (-) . Looking at how quickly I can
do this while at the PTS.
> On 13 May 2017, at 12:27, Jan-Olof Hendig (via RT)
> wrote:
>
> # New Ticket Created by Jan-Olof Hendig
> # Please include the string: [perl #131303]
> # in the subject line of all fut
The problem was actually in setting values in (Bag|Mix)Hash. The problem could
be golfed to:
my $b = BagHash.new; $b = 42; $b.total
Fixed in https://github.com/rakudo/rakudo/commit/4c813666df . Tests needed
> On 13 May 2017, at 12:27, Jan-Olof Hendig (via RT)
> wrote:
>
> # New Ticket C
> On 19 May 2017, at 23:56, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131330]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131330 >
>
>
>
> Detective
> On 20 May 2017, at 13:05, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131332]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131332 >
>
>
> By hypering
> On 20 May 2017, at 13:20, mt1957 (via RT)
> wrote:
>
> # New Ticket Created by mt1957
> # Please include the string: [perl #131333]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131333 >
>
>
> in perl version 2017.0
FWIW, I can’t get this to break on 2017.05. Please note that a *LOT* of
concurrency fixes landed after 2016.04. I suggest you use a more current
version, preferably 2017.05. Unless this problem can be confirmed on a more
recent Rakudo version, I suggest this ticket can be closed.
> On 25 May
Thanks for the report!
Fixed with https://github.com/rakudo/rakudo/commit/87d0e0a39e . Tests needed.
> On 28 May 2017, at 03:46, hanenkamp (via RT)
> wrote:
>
> # New Ticket Created by hanenkamp
> # Please include the string: [perl #131386]
> # in the subject line of all future corresponde
> On 26 May 2017, at 12:59, Peter du Marchie van Voorthuysen (via RT)
> wrote:
>
> # New Ticket Created by Peter du Marchie van Voorthuysen
> # Please include the string: [perl #131372]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Disp
> On 28 May 2017, at 20:56, brian d foy (via RT)
> wrote:
>
> # New Ticket Created by "brian d foy"
> # Please include the string: [perl #131392]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131392 >
>
>
> It looks li
> On 29 May 2017, at 18:26, brian d foy wrote:
> I did pull my first example out of a slightly larger program I was
> playing with, but I thought that a match would surely have no effect.
> Stupid me, because I've been around long enough to know that
> assumption is almost always false. That "harm
> On 29 May 2017, at 19:06, Zoffix Znet via RT
> wrote:
>
> https://irclog.perlgeek.de/perl6/2017-05-29#i_14654174
>
> 16:54 bisectable6 MasterDuke, bisect log:
> https://gist.github.com/7d49ce1401bee0ab3127c5d1be2a919e
> 16:54 MasterDuke, (2017-01-16)
> https://github.com
Fixed with 1ed284e2953382744b02058a , tests needed.
> On 31 May 2017, at 04:20, raiph (via RT) wrote:
>
> # New Ticket Created by raiph
> # Please include the string: [perl #131406]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.
Fixed with cb82760625f6b8fec64a75 , tests needed.
> On 31 May 2017, at 07:20, brian d foy (via RT)
> wrote:
>
> # New Ticket Created by "brian d foy"
> # Please include the string: [perl #131408]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/
> On 31 May 2017, at 19:53, Kais Ben Salah (via RT)
> wrote:
>
> # New Ticket Created by Kais Ben Salah
> # Please include the string: [perl #131412]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131412 >
>
>
> Hello,
Could you please retry on 2017.05? I cannot reproduce the problem, even after
1000 runs.
> On 30 May 2017, at 17:25, Sverre Eldøy wrote:
>
> Hi! Sorry for the late reply. I just tried it on 2017.04 ... and the problem
> is still there.. So please reopen
>
>
>> On 29 May 2017, at 20:53, Will
> On 5 Jun 2017, at 19:30, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131515]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131515 >
>
>
> Recently, we
Thanks for the report! Fixed with
https://github.com/rakudo/rakudo/commit/bf95bcb6c0
Tests will be added shortly.
> On 13 Jun 2017, at 00:52, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131561]
> # in the subject line of all
Shouldn’t:
sub ($ is rw) { }
be a compile-time error? I mean, there is no way to actually assign to the
anonymous variable, is there? So there is no point in the “is rw”. So most
likely indicates a typo on the user side.
> On 29 Jun 2017, at 01:05, Zoffix Znet (via RT)
> wrote:
>
> # N
> On 4 Jul 2017, at 16:05, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
> On 2017-07-04 05:29:20, comdog wrote:
>> Accessing a List element beyond the end of the List returns Nil,
>> although accessing an element before the beginning returns an out of
>> bounds failure. I think there's two th
> On 4 Jul 2017, at 16:19, Elizabeth Mattijsen wrote:
> That said, a List may not always be completely reified already. So
> logically, a List may have 100 elements, it could well be that only 42 of
> these elements exist already. Which means that the underlying NQP array,
> which *is* mutab
> On 11 Jul 2017, at 15:34, Jarkko Haapalainen (via RT)
> wrote:
>
> # New Ticket Created by Jarkko Haapalainen
> # Please include the string: [perl #131737]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131737 >
>
>
I’m inclined to WONTFIX, as other, much more common, indexing operation suffer
from the same issue:
$ 6 'my @a; say @a[999]'
Cannot unbox 64 bit wide bigint into native integer
$ 6 'my @a[999]'
Illegal dimension in shape: 999. All dimensions must b
> On 23 Jul 2017, at 03:48, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131783]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131783 >
>
>
> The current b
> On 23 Jul 2017, at 22:27, Sam S. via RT wrote:
>
>> Which then goes back to: what is the use case of Slipping an Array?
>
> Same as slipping any other type of Iterable: Fine-grained, elegant flattening
> and concatenating.
>
> Compare:
>
> my @all = flat $first, @rest;
>
> my @all = $fi
> On 24 Jul 2017, at 19:51, Zoffix Znet via RT
> wrote:
>
> On Mon, 24 Jul 2017 07:15:54 -0700, ju...@tnx.nl wrote:
>> It would be more awesome if "Unexected named argument 'foo' passed" was
>> supplemented with the name of the function to which it was passed.
>>
>>sub xyzzy ($x, :$foo = F
Looking at the profile of
(^1).grep({!/1/}).elems.say
the first 5 entries (responsible for 70% of CPU in that example) have nothing
to do with matching, but everything with trying to find the right dispatchee.
And it looks like this is basically caused by:
$_ = 1; /1/
Because $_
It’s really in the dispatch within Cool. Note the difference between:
for ^1 { 1.match(/1/) }
and:
for ^1 { "1".match(/1/) }
I’m afraid this is really uncovering a basic dispatch caching issue.
I have tried a few things, but I’m afraid this is really an issue inside
“find_best_di
> On 1 Aug 2017, at 14:36, Zoffix Znet via RT
> wrote:
>
> Turns out the rabbit hole goes deeper. Adverbs appear to not work if slice is
> structured:
>
>my %a = 'a'..'z';
>dd %a{, (, ('m', ('o')))}:kv; # OUTPUT: ()
>%a{, (, ('m', ('o')))}:delete;
>dd +%a.keys; # OUTPUT: 13
>
> On 1 Aug 2017, at 14:40, Александр Кирюхин (via RT)
> wrote:
>
> # New Ticket Created by Александр Кирюхин
> # Please include the string: [perl #131827]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131827 >
>
>
>> m
This should be fixed with 7599e0c3ffb2c7ef29c2994c , which reverted a256c26d850
> On 2 Aug 2017, at 16:21, Александр Кирюхин (via RT)
> wrote:
>
> # New Ticket Created by Александр Кирюхин
> # Please include the string: [perl #131830]
> # in the subject line of all future correspondence abou
> On 5 Aug 2017, at 00:43, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131842]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131842 >
>
>
> 20:49 ufobat
Added to my todo list
> 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.perl.org/Ticket/Display.html?id=131846 >
>
>
> Prev
Oops. Caught by a copy-pasto. Fixed with a91ad2da854831a7a38c1d , tests
needed.
> On 7 Aug 2017, at 20:59, Brad Gilbert (via RT)
> wrote:
>
> # New Ticket Created by Brad Gilbert
> # Please include the string: [perl #131855]
> # in the subject line of all future correspondence about this
reverted c63c57e9a823303e74c06 for now
> On 8 Aug 2017, at 12:21, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #131858]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display
Fixed with https://github.com/rakudo/rakudo/commit/c229022cb0 , tests needed
> On 12 Aug 2017, at 14:36, Peter du Marchie van Voorthuysen (via RT)
> wrote:
>
> # New Ticket Created by Peter du Marchie van Voorthuysen
> # Please include the string: [perl #131887]
> # in the subject line of al
This appears to be forgetfulness of the REPL from one input to the next. If
you put it on the same line, it *does* work:
> sub postfix:<€> (Int $n) {2*$n}; say 42€
84
So this boils down to a much more generic issue, for which we already have
tickets I believe.
> On 15 Aug 2017, at 14:25, Patr
Further datapoints:
$ perl6
To exit type 'exit' or '^D'
> sub postfix:<€> (Int $n) {2*$n}; say 42€
84
> say postfix:<€> (42)
84
So, the sub *does* survive from one call to the next. It only loses the
grammar adaptations that defining a sub postfix:<> do.
> On 15 Aug 2017, at 21:06, Elizabet
> On 17 Aug 2017, at 17:50, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #131919]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
> 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
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 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 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
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 ./
> 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 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
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 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 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
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 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 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
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 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 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 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
> 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
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 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
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
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 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.
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
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
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
Ah, indeed, so a workaround would be:
my $lock = Lock.new;
my $set = SetHash.new;
await ^16 .map: {
start {
for ^1 {
$lock.protect: { $set<1> = True; 1 }
$lock.protect: { $set<1> = False; 1 }
}
}
}
So maybe a solution would be to test for Proxy of the retu
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
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:
>>
> 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
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
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
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
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
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
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
> 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 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(
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
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
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 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)
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
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
On 22 Sep 2014, at 20:55, Paul Marquess (via RT)
wrote:
> # New Ticket Created by Paul Marquess
> # Please include the string: [perl #122827]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=122827 >
>
>
> The following on
unit sub ???
I thought that unit was only supposed to be followed by a package like
declaration??
> On 26 Mar 2016, at 02:10, Trey Harris (via RT)
> wrote:
>
> # New Ticket Created by Trey Harris
> # Please include the string: [perl #127785]
> # in the subject line of all future correspon
> On 27 Mar 2016, at 16:05, Itsuki Toyota (via RT)
> wrote:
>
> # New Ticket Created by Itsuki Toyota
> # Please include the string: [perl #127793]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127793 >
>
>
> It seems
d C that are intended
> to be run from the command line.
>
>
> On Sat, Mar 26, 2016 at 7:02 AM Elizabeth Mattijsen via RT
> wrote:
> unit sub ???
>
> I thought that unit was only supposed to be followed by a package like
> declaration??
>
>
> >
> On 11 Apr 2016, at 15:19, Itsuki Toyota (via RT)
> wrote:
>
> # New Ticket Created by Itsuki Toyota
> # Please include the string: [perl #127879]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127879 >
>
>
> See the
> On 01 May 2016, at 16:43, Itsuki Toyota (via RT)
> wrote:
>
> # New Ticket Created by Itsuki Toyota
> # Please include the string: [perl #128049]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=128049 >
>
>
> See the
Welcome to the world of floating point accuracy.
This little program typically ends within 100 iterations for me:
$ 6 'my int $a = 0; $a++ while (1..^(1+10e-15)).rand < 1+10e-15; say $a’
96
Either we dismiss this bug as being caused by lack of floating point accuracy,
or we build in something s
The parameters received from the command line, are always Str (or IntStr if
they look like an integer). To allow direct matching / handling of this, we
would need something like an EnumStr type. I don’t think that’s going to
happen soon.
I also tried some pre-processing on the @*ARGS array in
After some more investigation it turned out to be not so difficult in the MAIN
parameter
handling case. So, fixed with 546dbd99b18425a42c8 . Tests needed!
> On 18 Nov 2016, at 15:40, Itsuki Toyota (via RT)
> wrote:
>
> # New Ticket Created by Itsuki Toyota
> # Please include the string: [
1 - 100 of 101 matches
Mail list logo
