[perl #132668] [NATIVECALL][SEGV][SEVERE] OpenSSL PEM_write_bio_RSAPrivateKey

OK, so that's not an issue in Rakudo then. Closed. On 2019-03-05 11:16:41, sortiz wrote: > The problem is the PEM_write_bio_RSAPrivateKey signature used in the > NativeCall declaration, it missed five arguments. > > From the manual: > > int PEM_write_bio_RSAPrivateKey(BIO *bp, RSA *x, const

[perl #130442] [REGRESSION] [LTA] redo without a loop no longer prints the line number, also claims it is a compile-time error (redo)

Moved to https://github.com/rakudo/rakudo/issues/2725 On 2016-12-29 14:43:03, alex.jakime...@gmail.com wrote: > Of course, same thing with “next” and “last” (is there anything else?) > > On 2016-12-29 09:13:24, alex.jakime...@gmail.com wrote: > > Code: > > say 42; redo > > > > > > Result

[perl #131297] [PERF][REGEX] `|@a` is apparently-equivalent to just `@a` but is 70x slower

Closing, explanation here: https://github.com/rakudo/rakudo/issues/2708 On 2017-05-12 07:52:34, c...@zoffix.com wrote: > https://irclog.perlgeek.de/perl6-dev/2017-05-12#i_14572067 > > 14:49 m: my @a = 1..12; for ('a' x 100 ~ " -- Jan-12-2017") > xx 100 { when /'-- ' |@a '-' \d**2 '-' \d**4 / { }

[perl #125690] [BUG] Rakudo has stopped matching a regex, related to | vs. ||

Ticket moved to https://github.com/rakudo/rakudo/issues/2697 On 2015-09-25 14:06:27, duff wrote: > On Sat Jul 25 12:03:18 2015, moritz wrote: > > This script here: > > > > # BEGIN SCRIPT > > my grammar PgTokenizer { > > token double_quote_normal { <-[\\"]>+ } > > token double_quote_escape { [\\ .

[perl #133791] perl 6 parser bugging out on a comment thinking it is a real var

Usually this happens when you have an unclosed string somewhere earlier in your code. That is: say "foo; ← oops! Forgot the closing " # $a ← we think that this is a comment, but actually it's part of the string above! On 2019-01-23 01:27:08, warren.mu...@gmail.com wrote: > Hello: > > I ran into

[perl #75592] [LTA] Long running unclosed quotes trigger unhelpful message

I'm slightly confused by this ticket… isn't it resolved now? Nowadays you get an error message like this: Unable to parse expression in single quotes; couldn't find final "'" (corresponding starter was at line 2) So while it blows up at the end of the file, it still mentions where the quote

[perl #131392] [@LARRY] Remove magic $/ shortcuts %() and @()

Further discussion on https://github.com/rakudo/rakudo/issues/1946 On 2017-05-28 21:20:08, c...@zoffix.com wrote: > On Sun, 28 May 2017 18:18:14 -0700, raiph wrote: > > If there hasn't been significant adoption of these tokens in extant > > code then I'd personally +1 deprecation of them in v6.d

[perl #133268] MoarVM with empty CONTROL {}

Golf: CONTROL {}; warn 42 On 2018-06-08 15:11:08, comdog wrote: > While running this program I get a MoarVM panic: > > 2 + 2 = 4 > 'two' is not numeric > MoarVM panic: Trying to unwind over wrong handler > > The program: > > sub add-two-things ( $first, $second ) { > CATCH { > when

[perl #130774] [BUG] Rational.REDUCE-ME has a data race

The issue with .unique was resolved in these commits Rakudo: https://github.com/rakudo/rakudo/commit/8cd70d1ee3e17fad78ae5daf0890d1cfb74c2deb Roast: https://github.com/perl6/roast/commit/ad38801161c518a3cf3bca9012db973851c4b0c3 Roast:

[perl #132281] [REGRESSION] .gist of a bag used to say “bag()”, now it says “Bag()” ("blogger".comb.Bag)

https://github.com/rakudo/rakudo/pull/1722#issuecomment-380779444 On 2017-10-12 22:37:24, alex.jakime...@gmail.com wrote: > Code: > say "blogger".comb.Bag # if you want for all the letters > > ¦«2015.12»: > bag(r, l, g(2), b, e, o) > > ¦«2016.06»: > bag(r, l, g(2), b, e, o) > > ¦«2016.12»: >

[perl #122980] [BUG] LTA error message on fairly strange input, complaining about the lack of a semicolon when the semicolon's right there in Rakudo

Tests were added in this PR: https://github.com/rakudo/rakudo/pull/1715 Closing On 2017-12-02 04:17:46, alex.jakime...@gmail.com wrote: > Not quite sure what to do with this ticket. > > The output varies across releases: > https://gist.github.com/Whateverable/54e87afdbb2d88d2a959527b255681af > >

[perl #126752] [BUG] $/ vs .hyper gets confused

Test added in https://github.com/perl6/roast/commit/1f171a9d2f0dd973a5e0d5c0c34a6f50b91da81f Closing On 2018-03-08 10:28:12, jan-olof.hen...@bredband.net wrote: > On Fri, 27 Nov 2015 12:30:15 -0800, zengargo...@gmail.com wrote: > > autarch noticed an oddness in File::Temp when used with .hyper:

[perl #126394] [BUG] Assigning Failure to typed variable swallows Failure information

jmerelo++, tests added in https://github.com/perl6/roast/commit/ce173d4c6602333fac3dc8c1c8c2ec1b0b07c0ae Closing On 2015-10-19 07:43:11, larry wrote: > On Mon Oct 19 07:02:44 2015, elizabeth wrote: > > Fixed with a31cc91a0d604a8a74529 . Tests are still needed > > > > > On 19 Oct 2015, at 03:42,

[perl #125384] Could not find symbol '' in installed module, local version works fine.

jmerelo++ brought this ticket to my attention during the squashathon and suggested that this ticket can be closed. I've tried reproducing the issue with the provided tarball and couldn't. In fact, the Makefile in that tarball no longer works as expected because things are very different now.

[perl #131858] [REGRESSION] default $.nl-in on IO::Handle does not correctly work in subclasses

There's now a regression test in https://github.com/perl6/roast/commit/a7af87465e0dc593f4e008d6dcfe077f1bbff0f1 Closing (but please take a look at that roast commit) On 2018-03-11 13:11:21, jan-olof.hen...@bredband.net wrote: > On Tue, 08 Aug 2017 04:19:24 -0700, elizabeth wrote: > > reverted

[perl #131623] [BUG] Range + detached method + map with = "Cannot find method 'count' on object of type NQPMu"

A test for this issue was already added in https://github.com/rakudo/rakudo/commit/f3efe5e6b4a9ee5#diff-2aaee6bee3c5525182362ffdcbea1f2cR14 Closing. On 2018-03-10 16:40:40, jan-olof.hen...@bredband.net wrote: > On Thu, 22 Jun 2017 05:25:08 -0700, c...@zoffix.com wrote: > > A WhateverCode

[SPAM:##] [perl #126014] Too many repetitions with xx operator causes out of memory; should it work lazily?

Tests in https://github.com/perl6/roast/commit/b320464868d3b8da98c090ddc4b0d57604683e13 Closing On 2018-03-10 11:25:06, jan-olof.hen...@bredband.net wrote: > On Wed, 22 Feb 2017 03:59:05 -0800, elizabeth wrote: > > > On 22 Feb 2017, at 12:41, jn...@jnthn.net via RT > > follo...@perl.org> wrote:

[perl #126312] [BUG] `for @a` is not creating containers for uninitialized elements

Tests added in https://github.com/perl6/roast/commit/d78f33966cf6a6ec6bc060d98dfc521ad59b6f75 Closing On 2018-02-06 14:12:56, jan-olof.hen...@bredband.net wrote: > On Sat, 07 May 2016 13:26:09 -0700, sml...@gmail.com wrote: > > Confirmed on current Rakudo. > > > > Interestingly, it works if `for

[SPAM:##] [perl #132030] [TESTNEEDED] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout (buffering)

Tests added in https://github.com/perl6/roast/commit/40edf6d2c939fe095a848056db3489d7b1482a8a I think we can close this. On 2017-09-16 19:58:20, alex.jakime...@gmail.com wrote: > Two of the mentioned modules have pending pull requests that add > missing .close > calls in tests. NCurses module is

[perl #130941] infix: keeps containers around since October, resulting in confusing behaviour

Tests in https://github.com/perl6/roast/commit/1a42efd4ce0fdc695b16bbf64af92ecf0bca1866 On 2018-03-10 10:43:14, alex.jakime...@gmail.com wrote: > This ticket now needs tests, further discussion related issues here: > https://github.com/rakudo/rakudo/issues/1607 > > On 2017-03-08 05:56:13,

[perl #126490] [BUG] Control exception handling is inconsistent and broken across backends. (SEGV on moar, CX unrecognized on jvm)

Segfault mentioned above is already tested and the test was unfudged in https://github.com/perl6/roast/commit/ef7b0da83d#diff-72b101ff62a0582672d4de2788ffa1bbL77 Closing On 2018-03-12 08:29:49, jan-olof.hen...@bredband.net wrote: > On Mon, 16 Oct 2017 13:04:48 -0700, barto...@gmx.de wrote: > > On

[SPAM:##] [perl #130505] [LTA] double SORRY (BEGIN (1, 2)[*-1])

Tests in https://github.com/perl6/roast/commit/79dff96fc9f383616dd192ef016725395323887b and https://github.com/perl6/roast/commit/82d3a883a52af23c8a67e46b88b313b3cf20b18d On 2018-03-10 06:26:00, jan-olof.hen...@bredband.net wrote: > On Wed, 04 Jan 2017 15:02:45 -0800, alex.jakime...@gmail.com

[perl #126318] [BUG] trait 'is default' on attributes has no effect

Tests in https://github.com/perl6/roast/commit/ce1a5a2e6b5b199c0df69a83cf66f1b830ee47e8 and https://github.com/perl6/roast/commit/38c9dc5fd5339ed434438eb58bae07e7fdd31a1d Closing. On 2018-03-12 06:59:31, jan-olof.hen...@bredband.net wrote: > On Wed, 13 Sep 2017 19:17:16 -0700, b...@abrij.org

[perl #133017] First intermediate value of reduction with zip operator

Some extra info: Output on all releases (not a regression because the output was always wrong): https://gist.github.com/b4b27b8088a230a6051d634dc7b2d13e The change in behavior happened in (2017-03-21) https://github.com/rakudo/rakudo/commit/16f950b30572e0fa584ddfab1e84e5ef0ca5dfc9 Which links

[perl #133016] Wrong set difference of Bag and List

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) ) On 2018-03-24 01:43:59, elizabeth wrote: > That does indeed look wrong to me, investigating > > > On 23 Mar 2018, at 15:04,

[perl #126381] [CONC] Proc::Async has no way to get to a child's PID

Closing this in favor of https://github.com/rakudo/rakudo/issues/1638 On 2015-10-17 06:27:53, r...@hoelz.ro wrote: > As far as I can tell, MoarVM doesn't pass any information about a > child process' PID to the caller of async proc operations; if it does, > that information isn't exposed at the

[perl #126380] [NYI] Proc.pid

Closing this in favor of https://github.com/rakudo/rakudo/issues/1638 On 2017-10-02 00:09:23, alex.jakime...@gmail.com wrote: > Oh, actually, I noticed it too a few months ago. And removed it. > https://github.com/rakudo/rakudo/commit/5b8d4c2f4232dc0e5e9c62dc602fdcb74f7bdd24#diff- >

[perl #130586] [REGEX] "Iteration Past End" with Empty Character Class that has unescaped space in it

Further discussion on https://github.com/rakudo/rakudo/issues/1622. On 2017-01-21 14:13:42, jn...@jnthn.net wrote: > On Wed, 18 Jan 2017 18:16:20 -0800, c...@zoffix.com wrote: > > the :sigspace adverb does not affect spaces inside character class. > > Should it? > > > No, I don't think so.

[perl #132909] [LTA?] Failure return from require when load fails

Pretty sure this is a dup of https://github.com/rakudo/rakudo/issues/1515 , you can follow the progress on the issue there. Let us know if your problem is actually different. Closing On 2018-02-25 11:11:55, mt1...@gmail.com wrote: > Hi, > > According to the documentation one should use the

[perl #127093] gist missing for non-native typed array that doesn't get initialized

OK this issue is resolved with the commit mentioned above. Tests needed. As for *int* native array having NaNs in it, that's not going to happen. It's an array of native ints, it just can't and won't ever store any other type of a value. A native int can't be NaN. On 2016-01-02 06:34:50,

[perl #131914] [REGRESSION] Rakudo/Moar taking more memory at launch.

Interestingly, I can't reproduce it as well… But the numbers are still higher than they were, so I guess the ticket is valid? Here's the output on all releases: https://gist.github.com/Whateverable/8687cceb1bfcf39e9818cef819d29391 I'd say we can close it once we go back to 50-ish. On 2017-08-17

[perl #130493] [RFC][@LARRY] .sink of class not getting called, but Mu.sink is

I find the behavior surprising. Are there any examples of precedence thinkos that are caught by this? Added [RFC][@LARRY] tags, with just a little more information I think we'll be able to close. Maybe. On 2017-01-03 09:00:06, jn...@jnthn.net wrote: > On Tue, 03 Jan 2017 04:54:52 -0800,

[perl #130616] Wrong source line number reported for misspelled private class attribute names

Still reproducible: 6c: class Foo {␤ method foo {␤ say $!bad;␤ }␤ }␤ AlexDaniel, ¦6c (28 commits): «===SORRY!=== Error while compiling /tmp/Qj1o8IL3bG␤Attribute $!bad not declared in class Foo␤at /tmp/Qj1o8IL3bG:6␤--> ⏏␤ «exit code = 1»» On 2017-01-21 16:47:53, agen...@gmail.com wrote: >

[perl #130941] infix: keeps containers around since October, resulting in confusing behaviour

This ticket now needs tests, further discussion related issues here: https://github.com/rakudo/rakudo/issues/1607 On 2017-03-08 05:56:13, c...@zoffix.com wrote: > A temporary fix has been committed in > https://github.com/rakudo/rakudo/commit/5b7b7fb5c942a3e74097b5eb94a22be262f74c9f

[perl #126390] [BUG] await start {} hangs when using HTTP::UserAgent

FWIW it's not possible to reproduce the issue on older rakudos because it was sweeped under the rug in the URI module itself: https://github.com/perl6-community-modules/uri/issues/21 So yes, #126587 is a “testneeded” ticket for the underlying issue. On 2018-03-09 12:58:27,

[perl #126587] [SEGV] require inside thread segfault hang

dogbert++ noticed me that this issue is resolved (according to the provided snippets). It is indeed so. Second snippet may need this change: -return 200, ['Content-Type' => 'text/plain'], 'we win'; +return 200, ['Content-Type' => 'text/plain'], ['we win']; I can confirm that both issues are not

[perl #128520] [META][RT][RFC] Consider migrating from RT

OK, there's now a follow-up ticket here: https://github.com/rakudo/rakudo/issues/1598 On 2018-03-08 00:39:56, steve.myn...@gmail.com wrote: > Maybe the ticket should be closed if/when the RT bug tracker is closed > to new tickets itself and references to RT removed from all docs? > > S > > On 5

[perl #132012] [SEVERE] Numeric values of signals are wrong (say +SIGUSR1)

Further discussion on https://github.com/rakudo/rakudo/issues/1588 On 2017-10-18 03:46:20, c...@zoffix.com wrote: > On Sat, 14 Oct 2017 08:29:50 -0700, c...@zoffix.com wrote: > > Something fishy going on with the Signals enum. If that's fixed then > > the > > regression you pointed out will be

[perl #131626] [PERFTEST][PERF] ≥ and ≤ are 36x slower than Texas version; ≠ is 15x slower

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 Sep 2017 11:03:11 -0700, c...@zoffix.com wrote: > > On Thu, 22 Jun 2017 10:29:59 -0700, c...@zoffix.com wrote: > > >

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

On 2018-02-16 09:01:57, c...@zoffix.com wrote: > On Fri, 16 Feb 2018 05:52:09 -0800, elizabeth wrote: > > I propose we change all onlies in the core to multis after the release > > and see how this breaks things / makes things slower. > > +1. Let's try. Yeah, sounds good. +1

[perl #125618] [REGEX] Positional capture of separator on ?% operator causes compiler error

So I looked at this, and at very best the proposed error message is wrong. It says that ? is useless when used with %%, but that's not the case: m: say ‘af’|‘a’|‘f’|‘’ ~~ /a? %% f/ rakudo-moar 00af9ce27: OUTPUT: «｢af｣␤｢a｣␤｢f｣␤｢｣␤» m: say ‘af’|‘a’|‘f’|‘’ ~~ /a?f?/ rakudo-moar 00af9ce27:

[perl #129114] [BUG] state variable declared inside of a {} interpolation in a string, attaches to wrong scope

Just to clarify, the last snippet now produces 0 0 0 0, which is indeed correct. There are tests for this change in general, but possibly not for that particular case. Can we get it covered just in case? ｢testneeded｣ On 2018-02-06 05:51:23, jan-olof.hen...@bredband.net wrote: > On Sun, 28 Aug

[perl #131813] Segfault with --profile

Actually, I've been trying to reproduce it on the said revision with --profile, --ll-exception and whatnot, and I can't. I think this is an issue on OS X and therefore should be confirmed (and tested) on OS X also. On 2018-01-06 12:59:07, jan-olof.hen...@bredband.net wrote: > On Fri, 28 Jul 2017

[perl #132328] [SEGV][REGRESSION] DBIish tests are failing spectacularly (JIT compilation of native calls)

Honestly, I have no idea how to test this… maybe someone should attempt to golf it, but given that the commit description is “JIT compile native calls”, I guess it'd be a bit complicated. … I'm fine with just delegating it to the DBIish test suite… On 2017-10-20 08:12:41,

[perl #129787] [CONC] die/CATCH inside a start-block with a channel heisenbugs

FWIW, this bug is somewhat similar in feel: https://github.com/rakudo/rakudo/issues/1202 On 2017-10-15 03:14:02, c...@zoffix.com wrote: > On Wed, 02 Nov 2016 07:13:26 -0700, jn...@jnthn.net wrote: > > On Sun Oct 02 12:52:45 2016, gfldex wrote: > > > sub f(){ > > > my $c = Channel.new; > > > > > >

[perl #112986] [REPL] error 'Use of uninitialized $_ of type Any in numeric context" throws extra errors

 Test in https://github.com/rakudo/rakudo/commit/4385e3fc0b5272a14c1c507ccf5846684c16453a On 2017-08-28 13:58:57, alex.jakime...@gmail.com wrote: > Currently it says this: > Use of uninitialized value of type Any in numeric context > in block at line 1 > > As well as complains about sink

[perl #125299] [BUG] LTA error message when forgetting to close block inside string in Rakudo

Tests here: https://github.com/perl6/roast/commit/2dd5ee1b5935fce03eb815f8336ed26e019d4413 Resolved. Further discussion on https://github.com/rakudo/rakudo/issues/1475 On 2017-12-02 14:39:07, alex.jakime...@gmail.com wrote: > https://irclog.perlgeek.de/perl6/2017-12-02#i_15524141 > > Marking as

[perl #125985] [BUG] Internal error when a constant, unspace, and a map are involved in Rakudo

Anyway, tests in https://github.com/perl6/roast/commit/7557eef426fa4ea102d2d89b84c47dd5c1d3ab08 On 2018-02-03 14:40:09, alex.jakime...@gmail.com wrote: > Ouch. It seems that one of my links is wrong, should've been this one > I think: >

[perl #125985] [BUG] Internal error when a constant, unspace, and a map are involved in Rakudo

Ouch. It seems that one of my links is wrong, should've been this one I think: https://gist.github.com/Whateverable/cedc8ef783acc22e8f07afa98f5ad7d6 On 2017-12-02 19:41:52, alex.jakime...@gmail.com wrote: > Not sure how it golfs down to that, because it never produced the same > error > message.

[perl #130261] [LTA] Error message for unclosed curly quote points to the last line of the file

Tests in https://github.com/perl6/roast/commit/ceabda6337364b5f1cec3c1c5bcb89787f9bcedf On 2018-01-08 15:18:46, alex.jakime...@gmail.com wrote: > Note that the error message is still LTA (says “corresponding starter” > instead > of mentioning “’”), for further progress see RT#125641. > > On

[perl #129296] Splitting non-binary handles no longer works (run(:out, "ls").out.split: 0.chr)

 Tests in https://github.com/perl6/roast/commit/3ca315596c3283c8cd168428065f01062c4633a5 On 2016-11-18 10:51:38, alex.jakime...@gmail.com wrote: > On 2016-11-18 10:38:48, coke wrote: > > On Sun, 18 Sep 2016 03:14:30 -0700, elizabeth wrote: > > > Fixed by reverting 1a03efe4e3b61a07b7df5 in

[perl #127100] [LTA] error message when specifying return type before parameters ( --> Bool, Int $x, Int $y )

Tests in https://github.com/perl6/roast/commit/3dab7c774587fbf8ae2afb561b02b3177659ace3 On 2017-10-07 15:55:27, alex.jakime...@gmail.com wrote: > This was resolved in these commits: > * > https://github.com/rakudo/rakudo/commit/ac97a4016196c1fb5c39365dfbe8980574fb929b > * >

[perl #127671] [EXOTICTEST] ｢dir｣ dies if weird unicode sequences are encountered (dir;)

Test added in https://github.com/perl6/roast/commit/a7590d6543e1d29bc935377c727e4d15e38ee713 Note that the test *does create* files with weird names, but that's totally OK in /tmp I think. On 2017-03-02 07:06:54, c...@zoffix.com wrote: > Explanation and ideas on IRC:

[perl #129882] [TESTNEEDED] [CONC] [IO] Proc with `.in.close` and `.out.slurp-rest` in different threads, hangs

Test in https://github.com/perl6/roast/commit/195227f779f7441de1678e12941550271da799b2 On 2017-07-09 19:40:57, alex.jakime...@gmail.com wrote: > That's pretty good. But issues are not closed without tests, unless > there's a > good reason not to add a test. No reason was mentioned, therefore >

[perl #125674] [LTA] error message prints wrong eject position (if True if { };)

Does not seem to be fixed at all. But I've added some todo-ed tests: https://github.com/perl6/roast/commit/f9f5034a1e66e068bfe21227e35f100f3c1e3fef On 2017-10-07 13:43:30, alex.jakime...@gmail.com wrote: > Should be fixed in https://github.com/rakudo/rakudo/commit/5747bc7121 > > Testneeded.

[perl #132741] [BUILD] Broken on FreeBSD and OpenBSD

This was fixed, for more info see this still-open issue: https://github.com/rakudo/rakudo/issues/1420 On 2018-01-19 07:30:48, steve.myn...@gmail.com wrote: > MoarVM build broken on FreeBSD 11 and OpenBSD 6.2 > > .. > > Configuring and building MoarVM ... > /usr/local/bin/perl5 Configure.pl

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

Yes, it would be awesome to have warnings for unused params and variables. On 2018-01-14 12:16:08, c...@zoffix.com wrote: > On Sat, 14 Oct 2017 20:53:03 -0700, alex.jakime...@gmail.com wrote: > > FWIW I made a throwaway script that looks for unused params, and > > there > > are many > > of these

[perl #132718] BUG: Unhandled kind 3 with int32 argument

FWIW it was “working” before this commit: https://github.com/rakudo/rakudo/commit/ec18f24d27ce61fa71d177ab76c4044ee1d1a75e But that's probably irrelevant because I'm pretty sure it was cheating with something. On 2018-01-13 13:56:54, elizabeth wrote: > > > On 13 Jan 2018, at 22:38, Curt Tilmes

[perl #132718] BUG: Unhandled kind 3 with int32 argument

FWIW it was “working” before this commit: https://github.com/rakudo/rakudo/commit/ec18f24d27ce61fa71d177ab76c4044ee1d1a75e But that's probably irrelevant because I'm pretty sure it was cheating with something. On 2018-01-13 13:56:54, elizabeth wrote: > > > On 13 Jan 2018, at 22:38, Curt Tilmes

[perl #130261] [LTA] Error message for unclosed curly quote points to the last line of the file

Note that the error message is still LTA (says “corresponding starter” instead of mentioning “’”), for further progress see RT#125641. On 2018-01-08 15:16:47, alex.jakime...@gmail.com wrote: > Ah. This was fixed. Here's the pull request: > https://github.com/rakudo/rakudo/pull/1183 > And here's

[perl #130261] [LTA] Error message for unclosed curly quote points to the last line of the file

Ah. This was fixed. Here's the pull request: https://github.com/rakudo/rakudo/pull/1183 And here's the right commit: https://github.com/rakudo/rakudo/pull/1183/commits/6542bb8032e7203b8736655075dbd3452856bc93 There should be tests for this already, I think. On 2016-12-04 10:22:37,

[perl #131813] Segfault with --profile

Closable with rakudo tests then. On 2018-01-06 12:59:07, jan-olof.hen...@bredband.net wrote: > On Fri, 28 Jul 2017 15:52:53 -0700, timo wrote: > > It could be that the commit i just pushed to moarvm fixes this, > > please > > verify (the code doesn't crash with the patch) > > Seems to work

[perl #124679] [@LARRY] Rakudo allows using '#`' (embedded comment) without following opening bracket, should not

Ah. Now I see why. Consider this: #`| foo | ↑ that does not DWIM. And it's right to assume that you can do it because s||| works just fine. So either it should understand stuff like this, or it can give an error message as todo-ed. So no, this is not rejectable. And the actual issue is about

[perl #127881] [PERF] slow array slicing

FWIW this issue was noticed today: https://irclog.perlgeek.de/perl6/2017-12-16#i_15587006 On 2016-04-11 20:40:43, ddgr...@gmail.com wrote: > '@array[0, 3, 7]' is much slower than '(@array[0], @array[3], @array[7])' > > > time perl6 -e 'my @a = ^500;my @f;my $s = @a.elems;loop (my $i1 = 0; $i1 < >

[perl #127775] Declaring enums with Bools, IntStrs and maybe other things ( enum Foo (:Bar(1), :Baz(True) ))

I am pretty sure that this commit is relevant to this issue: https://github.com/rakudo/rakudo/commit/fc52143beee3178c7f39d770f95c7d60b2a1a1e4 On 2017-10-07 17:20:37, alex.jakime...@gmail.com wrote: > Zoffix++ pointed out that there is a problem with IntStr also: > > Code: > enum Foo (:Bar(1),

[perl #132525] [REGRESSION][PRECOMP] type constraints to Array[Pair] don't work when precompiled

Oh, by the way. The issue goes much farther than 2015.12, so the underlying issue is not a regression. On 2017-12-13 23:42:11, alex.jakime...@gmail.com wrote: > We can, but I'd much rather have this particular case tested (and to > make sure > that it is, we'll close it with tests once the issue

[perl #132525] [REGRESSION][PRECOMP] type constraints to Array[Pair] don't work when precompiled

We can, but I'd much rather have this particular case tested (and to make sure that it is, we'll close it with tests once the issue is resolved). For example, here's this interesting bit: https://github.com/rakudo/rakudo/blob/master/src/core/core_prologue.pm#L2 : my class Pair { ... } # must be

[perl #87034] [BUG] Either binding an array to a list containing the array itself should work consistently or not at all in Rakudo

By the way, there is a pull request: https://github.com/rakudo/rakudo/pull/1020 But the work on it is kinda stalled. On 2017-02-17 04:22:51, alex.jakime...@gmail.com wrote: > Reopened for now. > > See RT #121807 and RT #125371 for more info. Basically, there will be > no error > after I'm done

[perl #121987] Negated generic comparisons do not chain correctly

Closing this ticket in favor of this one: https://github.com/rakudo/rakudo/issues/1304 On 2017-12-01 11:03:43, alex.jakime...@gmail.com wrote: > Still failing (2017.11, HEAD(5929887)) > > On 2014-07-31 13:05:19, david.warring wrote: > > I've added some fudged tests to S03-operators/relational.t.

[perl #132511] Binary assignment Z+= fails if it's the last thing in for loop

FWIW it never worked: https://gist.github.com/Whateverable/d9dbebb0e985a3964845df2c8652cbdf On 2017-11-27 17:36:22, comdog wrote: > I previously asked about this unexpected Z behavior on Stackoverflow > ( https://stackoverflow.com/q/45001820/2766176 ). > > I expected this to change several hash

[perl #132487] Accessing the native-descriptor() from a Proc output seems to break it.

Some *able info, if anyone is interested: Output on all releases: https://gist.github.com/a68b094519839b939f8c70d66a80d8c0 Some possibly relevant commits: https://github.com/rakudo/rakudo/commit/92bd7e4f54a92fa660f99b4d056d33a08fb98bd2

[perl #122972] [NYI] Proto regex with params isn't called correctly (possibly NYI) in Rakudo

Still NYI (2017.11,HEAD(e5b660e)) On 2014-10-14 01:02:45, masak wrote: > m: grammar Test { token TOP { }; proto token > Foo(Int) {*}; token Foo:sym(Int $a) { "a" }; token Foo:sym(Int > $a) { "b" } }; say Test.parse("a"); > rakudo-moar 8b3e8c: OUTPUT«Too few positionals passed; >

[perl #122992] [BUG] Declaring a 'my' array or hash typed with a type parameter ends up blowing up with a fixable error message about instantiating generics in Rakudo

Seems to be reproducible (2017.11,HEAD(e5b660e)) On 2014-10-16 13:43:34, masak wrote: > camelia was having some indigestion in the below backlog, which is why > I'm reporting some local evals (from "This is perl6 version > 2014.09-202-g8b3e8c2 built on MoarVM version 2014.09-54-g03ac9a7"). > >

[perl #125200] [Bug] parametric role generic type not resolving early enough?

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-05-15 11:25:07, jdv79 wrote: > The first example there should have been: > > [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has Int @.a }; say > Foo[Int].new.a.WHAT' > (Array[Int]) > [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has T @.a }; say >

[perl #76744] [TODO] implement :dba adverbs in regexes

Related doc ticket (with some discussion): https://github.com/perl6/doc/issues/1695 On 2010-07-27 02:32:49, moritz wrote: > alpha supported :dba('rule name'), current Rakudo doesn't, but should.

[perl #126030] Multi-dim hash loses track of leaf type

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-09-09 22:28:41, larry wrote: > 22:22 < TimToady> m: my Bool %hash{*;*}; %hash{"a"; "b"} = True; > 22:22 <+camelia> rakudo-moar c54773: OUTPUT«Type check failed in assignment > to '%hash'; expected 'Bool' but got 'Hash'␤ in block > at

[perl #126116] [BUG] native type constraint inconsistently applied

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-09-20 09:07:10, zef...@fysh.org wrote: > Because a type object is an (undefined) instance of that type, it can > in general be stored in a variable constrained to that type. We can > demonstrate this with a subroutine taking a type parameter: > >

[perl #123903] [BUG] Some forms of "dynamic symbol lookup" syntax cause compiler error in Rakudo

As of today (2017.11,HEAD(e5b660e)) it gives this: ===SORRY!=== Error while compiling -e Variable '$' is not declared at -e:1 --> say defined ⏏$:: There was another ticket that had exactly the same change of an error message, perhaps worth searching for it (ping me if you really want to

[perl #122838] [BUG] BEGIN GLOBAL:: assignment does not work in Rakudo

As of today (2017.11,HEAD(e5b660e)) it prints this: Cannot call method 'new' on a null object in block at -e line 1 Which is arguably reasonable, but I guess it's not good enough. On 2014-09-24 04:03:12, masak wrote: > m: BEGIN GLOBAL:: = class { }; Test.new; > rakudo-moar 682e03:

[perl #122991] [TODO] Implement 'handles' for 'my'-scoped (class) variables in classes

Still reproducible (2017.11,HEAD(e5b660e)) (complains about trait_mod:) On 2014-10-16 13:07:07, masak wrote: > m: class A { my @.foo handles }; A.push("OH", "HAI"); > say A.foo > rakudo-moar a6f181: OUTPUT«(timeout)» > locally: "Cannot call 'trait_mod:'; none of these > signatures match"

[perl #126107] [BUG] "of" type constraint inconsistently applied

All of these were fixed (2017.11,HEAD(e5b660e)). Strings give compile-time errors, putting Any into something results in an Int. Curious minds can ask bisectable for details. ｢testneeded｣ On 2015-09-20 17:26:00, zef...@fysh.org wrote: > Extended case: if the "of" clause comes after an "is

[perl #123835] Cannot use 'is rw' on optional parameter

Still reproducible (2017.11,HEAD(e5b660e)) I don't know if it's NYI or @LARRY. I'd put LARRY first, and then one of the LARRYs can turn it into a NYI. On 2015-08-05 15:25:57, barto...@gmx.de wrote: > The relevant sentences from the design docs (S06, introduced with > commit 7846594ee4): > >

[perl #116783] [BUG] 'my' class in role should be generic in Rakudo

Output on all releases: https://gist.github.com/Whateverable/297882f4f84bb8362a0ce0523439c436 On 2013-02-16 09:14:04, masak wrote: > r: https://gist.github.com/TimToady/4963642 > jnthn: that gets me an error Nominal type check failed for > parameter '$payload'; expected T but got Int instead >

[perl #110820] [BUG] Variable declaration inside statement_modifier for inside junction triggers bogus redeclaration error in Rakudo

This wasn't updated in a while. As of today (2017.11,HEAD(e5b660e)), it still complains about final ) like mentioned in one of the recent comments. And yes, this tickets seems to be rejectable. On 2015-07-20 09:27:25, duff wrote: > I'm not sure this is a bug. The postfix for is a statement

[perl #124007] [BUG] method delegation doesn't work in roles

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-03-06 14:35:06, rayd...@cyberuniverses.com wrote: > As seen at http://irclog.perlgeek.de/perl6/2015-03-06#i_10237611 : > > r: role R { method foo () handles { } } > rakudo-moar 1b74e4: OUTPUT«===SORRY!=== Error while compiling >

[perl #125487] Possible MMD issue when binding nqp::null() ??

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-06-26 02:25:27, elizabeth wrote: > [10:57:16] m: use nqp; my %h; %h := nqp::null() > #h > [10:57:16] <+camelia> rakudo-moar 3d645f: OUTPUT«Unexpected named > parameter 'BIND' passed␤ in block at /tmp/GYnIiEF0VO:1␤␤» > > This looks strange

[perl #120394] [BUG] Can't access private attributes through the ::('$!x') syntax in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2013-10-28 02:49:38, masak wrote: > p: class A { has $!x = 42; method get() { ::('$!x') } }; say > A.new.get > rakudo-parrot 3cef56: OUTPUT«No such symbol '$!x' [...] > should that work? > moritz: my first thought is "I don't see why it

[perl #121166] [BUG] LTA error message when assigning to lexical variables from inside a regex in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)), almost identical error message. On 2014-02-04 08:01:17, masak wrote: > m: my $x; 'abc' ~~ /$x=(ab)/; say $x > rakudo-moar 44ab3c: OUTPUT«===SORRY!===␤Error while > compiling op bind: QAST::Block with cuid cuid_1_1391529188.76986 has > not appeared␤» >

[perl #117421] [BUG] Typing with ::SomeClass instead of SomeClass in 'has' declaration causes the wrong type object to end up in that attribute in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2013-03-30 16:55:04, masak wrote: > r: class A { has ::B $.b }; class B {}; print B.new; print > A.new.b.new > rakudo ba5e04: OUTPUT«B<-905822265>No such method 'new' for > invocant of type 'B'␤ in block at /tmp/TluLYMLqwz:1␤␤» > masak: ^^ hmm >

[perl #123507] Can't stat modules/debugger-ui-commandline/lib: No such file or directory

This is very old and nobody was complaining about this issue since then. I guess the problem is no longer there, but we won't be able to track it. Therefore, rejected (but I'm hoping that the underlying issue was actually resolved). On 2014-12-26 23:16:35, ga...@szabgab.com wrote: > During the

[perl #124226] [BUG] Opportunity to catch syntactically detectable calls to attribute-accessing methods on type objects in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-04-01 13:19:33, masak wrote: > <[Tux]> m: class C { has Int $!x; method foo { ($!x, my $b) = > (1,2);}};C.foo > 19:45 <+camelia> rakudo-moar 6caf1d: OUTPUT«Cannot look up attributes > in a type object␤ in method foo [...] > <[Tux]> is that

[perl #125343] [WEIRD] Using an earliest { ... wait 0 { ... } } causes

Alright. On 2017-12-03 00:53:04, elizabeth wrote: > 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 > > <perl6-bugs-follo...@perl.

[perl #124832] Roast rakudo skip/todo test:./S12-enums/basic.t line:24 reason: 'Cannot convert string to number'

This ticket is replaced with https://github.com/rakudo/rakudo/issues/1296

[perl #122289] [BUG] unexpected behaviour during EVAL()

Hmmm… Parrot is in the past as of today, and I wish it was possible to try this on MoarVM. What's the way to reproduce this issue? On 2014-07-14 02:31:54, teodozjan wrote: > Evaling objects won't work if code that eval was preompiled > independently. In this case class Planet and Class

[perl #124150] [BUG] Match.caps is inconsistent across backends

As of today (2017.11,HEAD(e5b660e)) it prints a *third* variant: (ident => ｢a｣ alpha => ｢a｣ alnum => ｢a｣) The change happened in (2017-02-22) https://github.com/rakudo/rakudo/commit/1cafc67b1aad14eafa8d3e6431656524e4d0d5d3 To me it tells that it is just random. On 2015-03-22 13:02:12,

[perl #124341] Proxy object also works on non- "is rw" subs/methods

What is this thing about? Was there a code snippet that got lost? On 2015-04-18 10:16:32, elizabeth wrote: > [19:13:51] if nothing else it showed that a Proxy leaks > through a not-is-rw method > [19:13:55] _mg_ (~anonymous@95.88.244.237) left IRC. (Client > Quit) > [19:13:57] Yes, that's a

[perl #125732] Subsignatures of a capture param not used to sort MMD candidates

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-07-31 19:09:17, b...@abrij.org wrote: > > # The following should all have the same result: > > $ perl6 -e 'multi a ($x) { 41.say }; multi a (@a) { 42.say; nextsame > }; a([1,2]);' > 42 > 41 > $ perl6 -e 'multi a (|c($x)) { 41.say }; multi a

[perl #125168] [NYI] a way to open files in "r+" mode in Rakudo

Isn't it implemented as :update now? https://docs.perl6.org/routine/open Or maybe you can even use :mode? (the documentation says that it will make the universe implode, but perhaps it's worth a try?) On 2015-05-13 02:11:06, masak wrote: > so, how do I open a file in update mode (fopen

[perl #126111] [BUG] coercive type constraint for variable inconsistently accepted

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-09-19 11:15:43, zef...@fysh.org wrote: > A coercive type constraint is not permitted on a variable: > > $ ./perl6 -e 'my Int() $a; say 1' > ===SORRY!=== Error while compiling -e > Coercion Int(Any) is insufficiently type-like to qualify a

[perl #125934] [BUG] &?ROUTINE changes to something else in gather in for loop

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-08-28 10:05:31, FROGGS.de wrote: > m: sub foo { say &?ROUTINE.perl; gather for 1 { say &?ROUTINE.perl; }; > gather for 1 { say &?ROUTINE.perl; } }; foo > rakudo-moar 5fb81f: OUTPUT«sub foo () { #`(Sub|59748232) ... > }␤Code.new␤Code.new␤» >

  1   2   3   4   5   >