[perl #132206] Compiler error on WhateverCode and chained comparisons

# New Ticket Created by Brandon Allbery # Please include the string: [perl #132206] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132206 > [03 05:10:36] m: subset MyStr of Str where 4 < *.chars < 10; my MyStr $s = 's'; [03

[perl #127096] [LTA] error message when doing weird base conversions ( :5<1.I> )

Actually, this is a dup of https://rt.perl.org/Ticket/Display.html?id=128804 , and I think it's now resolved. On 2015-12-30 12:39:37, alex.jakime...@gmail.com wrote: > Code: > say :5<1.I> > > Result: > ===SORRY!=== Error while compiling -e > Couldn't process entire number: 1/1 int chars, -1/1

[perl #132205] .gist of a Match should not print null bytes, and maybe other control chars too (say “\0” ~~ /<[\0]>/)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132205] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132205 > m: say “\0” ~~ /<[\0]>/ rakudo-moar fcbd8a: OUTPUT: «｢␀｣␤» … did

[perl #130186] Match object inside .comb is weird (‘789’.comb(/ . {say $/} /))

This was fixed during the uncurse merge. Bisect log (20 candidates): https://gist.github.com/7cedc2e2e35913544f75bc5fc89bd088 ｢testneeded｣ On 2016-11-26 18:36:35, alex.jakime...@gmail.com wrote: > *Code:* > dd ‘789’.comb(/ . {say $/} /)' > > *Result:* > ｢7｣ > ｢7｣ > ｢7｣ > slip() > > It may seem

[perl #126596] [LTA] confusing error with single '{' in double quoted string:

Oh. That's actually related to this ticket: https://rt.perl.org/Ticket/Display.html?id=132168 I'll merge it because both tickets are asking for the same problem to be resolved. On 2015-11-09 05:03:59, jns...@gellyfish.co.uk wrote: > perl6 -e 'my $a = "jsjsjs {"; for -> $b { say $b }' >

[perl #126574] Single named match does not work with hyper (».Str)

Interesting. On 2015-11-05 16:13:33, besc...@gmail.com wrote: > m: grammar G {rule TOP {}; token G1 {A}}; my $g = > G.parse("A"); say $g».Str > > rakudo-moar c880f1: OUTPUT«()» > > See: http://irclog.perlgeek.de/perl6/2015-11-05#i_11492065 > > and subsequent discussion.

[perl #128054] [PARSER] In a string enclosed in parens, a {}-interpolation can't access the topic $_ of a statement modifier

Also worth taking a look at https://rt.perl.org/Ticket/Display.html?id=126569 On 2017-09-29 14:06:58, b...@abrij.org wrote: > On Sun, 28 May 2017 00:08:18 -0700, sml...@gmail.com wrote: > > This bug is still present in > > > > This is Rakudo version 2017.05-134-g0c5fe56cc built on MoarVM version

Re: variable size limit?

On Mon, Oct 2, 2017 at 6:22 PM, ToddAndMargo > wrote: Hi All, I am about to pick up 5 MB of data and cram it into a $ variable. Is there some size limit to how much data I can or should cram into a variable? Many

Re: variable size limit?

I'd recommend using less memory in a variable than your system has in physical RAM, or your program will get slow from swapping to disk. I've never had a computer with less than 8MB of memory, so you should be fine. On Mon, Oct 2, 2017 at 6:22 PM, ToddAndMargo wrote: >

[perl #126375] [LTA] [NYI] error message leaks internal stuff: [SR-]

On Mon, 02 Oct 2017 18:21:29 -0700, alex.jakime...@gmail.com wrote: > It now prints a completely different error message. The major change > was in > https://github.com/rakudo/rakudo/commit/1628e485df1356ae51513009863998daacceffea > but see also how it was changing throughout the years: >

[perl #126375] [LTA] [BOOTSTRAP] error message leaks internal stuff: [SR-]

It now prints a completely different error message. The major change was in https://github.com/rakudo/rakudo/commit/1628e485df1356ae51513009863998daacceffea but see also how it was changing throughout the years: https://gist.github.com/555d070b47c007258bd51d95004c2e40 Code: say [SR-] Result: No

variable size limit?

Hi All, I am about to pick up 5 MB of data and cram it into a $ variable. Is there some size limit to how much data I can or should cram into a variable? Many thanks, -T

[perl #125555] [NYI] Comparison ops for DateTimes in Rakudo

I'd say it's TESTNEEDED for now. Maybe the the stuff from S03 should be spec-ed in tests and then we can have a separate ticket asking for these changes. On 2015-09-06 20:11:24, labster wrote: > Comparison ops added in dac0167a, but I still feel like this behavior > runs counter to S03#1332. > >

[perl #125523] [NATIVECALL] num64 not properly defaulting

Right, because it's a Rat. sub foo(num64 $scale = 1.0) {}; say foo # This type cannot unbox to a native number: P6opaque, Rat sub foo(num64 $scale = 1.0.Num) {}; say foo # Nil I don't know what is the consensus on this one, but having to .Num your values is rather reasonable. The error message

[perl #125277] [LTA] error message when using the wrong sigil with an @array or %hash

Yes, I'm happy with it too. No need for perl 5 error message here (also, please, let's have less perl 5 error messages). testneeded. Also, here's how the error message was changing over time: https://gist.github.com/Whateverable/2373e732b2c3c10f643fa8eb5c5470a7 On 2016-07-07 06:52:35, coke

[perl #125215] [BUG] 10 ** -1 is a Num, but should probably be a Rat since it can in Rakudo

Yes, this was fixed in https://github.com/rakudo/rakudo/commit/563abdd46845d70483a21180c817de516003309c Testneeded. On 2015-11-12 12:19:37, barto...@gmx.de wrote: > As a status update: 10 ** -1 is now a Rat: > > $ perl6-m -e 'say (10 ** -1).WHAT' > (Rat) > > 9.0 ** -1 is also a Rat, and there is

[perl #122750] [LTA] bug or error message not informative

Any ideas on what could be a better error message? On 2014-09-10 10:53:18, equinox wrote: > Hi all, > > > use NativeCall; > class TopWindow is repr('CPointer') { > multi sub TopWindow_TopWindow_c() returns OpaquePointer is > native("ultimatewindll") { * } #symbol('TopWindow_TopWindow_c') > >

[perl #125580] [BUG] bag/set related issues

Bisected. First issue was resolved in https://github.com/rakudo/rakudo/commit/11f27a30bdf380c53697330ec62e982dde68e0b0 On 2017-10-01 23:59:39, alex.jakime...@gmail.com wrote: > 1. I think it is properly guarded now. (error message: Cannot coerce a > lazy > list onto a Bag) > 2. That's OK. A lot

[perl #125820] [9999] .roll(-9999999999999999999999999999999999999999999999999)

See also https://rt.perl.org/Ticket/Display.html?id=125816 (same bisectable result) On 2017-10-02 17:12:02, alex.jakime...@gmail.com wrote: > FWIW, fix bisected (not precisely, but maybe this helps anyway): > * bisect log: https://gist.github.com/5049c109fce53fa78ff969a44ba66366 > * (2015-08-27)

[perl #125816] [9999] "x".indent(9999999999999999999999999999999999999999999999999)

FWIW bisectable gives the same result as in https://rt.perl.org/Ticket/Display.html?id=125820 On 2017-10-01 23:32:03, alex.jakime...@gmail.com wrote: > Now it complains about unboxing a large int. > > On 2015-08-14 21:07:37, alex.jakime...@gmail.com wrote: > > First part is OK, but once we start

[perl #125820] [9999] .roll(-9999999999999999999999999999999999999999999999999)

FWIW, fix bisected (not precisely, but maybe this helps anyway): * bisect log: https://gist.github.com/5049c109fce53fa78ff969a44ba66366 * (2015-08-27) https://github.com/rakudo/rakudo/commit/23b3d29da6ffd8e016ea6da6c34858b95339af34

[perl #125336] Weird infinite ranges: Inf..0, -Inf..0 and NaN..0

The problem went away during the glr. Bisectable points to 96 candidates, so nothing useful there. On 2017-10-01 23:15:28, alex.jakime...@gmail.com wrote: > I think that this stuff is resolved. Not sure when exactly because > bisectable > is refusing to work today, but this is TESTNEEDED. > > On

Re: <<>> question

On 10/02/2017 04:31 PM, ToddAndMargo wrote: is examples if ^ of

Re: <<>> question

On Oct 2, 2017 1:18 PM, ToddAndMargo wrote: Hi All, I am writing up a keeper note on <<>> and such.  This example puzzles me.  Why the space? Example of <<>> (double quote and allow insertion of variables into strings):     $ perl6 -e 'my $x="abc"; my

Tip: hash indexing

Hi All, I created a keeper not on hash indexing. I though maybe you guys would find it interesting, if for nothing else, for the syntax used -T Perl6: Indexing a hash: #!/usr/bin/env perl6 #`{ Hashes do not print in the order they are created. it is a Perl 6 thing. To overcome this,

<<>> question

Hi All, I am writing up a keeper note on <<>> and such. This example puzzles me. Why the space? Example of <<>> (double quote and allow insertion of variables into strings): $ perl6 -e 'my $x="abc"; my $y=<>; say "\$x=$x \$y=$y";' $x=abc $y=xyz abc def Many thanks,

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

Thanks, that helps. I wasn't sure where to file this bug, because this is the first time I've used Rakudo. What looks odd to me is the line Can't find string terminator '"' anywhere before EOF at -e line 1. which is presumably the command shell('perl -e "use v5.18;"') on the line you linked

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

Well spotted! Docs at https://docs.perl6.org/routine/shell may help But this looks to me to be a known issue "quote bug in shell command on windows" https://rt.perl.org/Public/Bug/Display.html?id=131814 On 2 October 2017 at 09:06, Ville Koskinen wrote: > Thanks,

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

Well spotted! Docs at https://docs.perl6.org/routine/shell may help But this looks to me to be a known issue "quote bug in shell command on windows" https://rt.perl.org/Public/Bug/Display.html?id=131814 On 2 October 2017 at 09:06, Ville Koskinen wrote: > Thanks,

Re: [perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

Thanks, that helps. I wasn't sure where to file this bug, because this is the first time I've used Rakudo. What looks odd to me is the line Can't find string terminator '"' anywhere before EOF at -e line 1. which is presumably the command shell('perl -e "use v5.18;"') on the line you linked

[perl #132195] Feature request: Have Test.pm6 tests accept an optional second description.

On Sun, 01 Oct 2017 18:16:34 -0700, tbrowder wrote: > On Sun, Oct 1, 2017 at 17:23 Zoffix Znet via RT > wrote: > > On Sun, 01 Oct 2017 10:10:55 -0700, tbrowder wrote: > ... > > My vote on this feature is a most definite -1. I see no reason to > > over-engineer a core

[perl #124455] substr on compact array

Also, the design docs say you get the same kind of buffer back from substr on a buf, but we have subbuf for that now.

[perl #124455] substr on compact array

The tests are bogus just the assumption that a substr of length 8 will give you 8 bits rather than 8 bytes, that's already wildly inconsistent with what substr does otherwise. really this code looks like the desire to have `vec` from perl5 implemented in perl6 by re-using the substr name. I

[perl #130604] [PARSER] Weirdness when mixing `..` and `...` without parens

Oh. Maybe it's https://rt.perl.org/Ticket/Display.html?id=127279 ? On 2017-08-26 08:01:06, alex.jakime...@gmail.com wrote: > Indeed, I'm not sure what I was smoking. > On 2017-01-20 21:27:50, sml...@gmail.com wrote: > > > It numifies ranges so that the number of elements is used. In other > > >

[perl #126805] [BUG] `make` fails with latest git - commit 734549a754224dbd18d1f5ef27d778933b12175c

Thank you for your report. Realistically, that's the end of that ticket. Obviously, ｢make｣ no longer fails, and who knows what was the problem back then. Given that the issue no longer happens I think it's fair to say that it is resolved. Feel free to reopen if you are still having issues with

[perl #126380] [NYI] Proc.pid is never set

Oh, actually, I noticed it too a few months ago. And removed it. https://github.com/rakudo/rakudo/commit/5b8d4c2f4232dc0e5e9c62dc602fdcb74f7bdd24#diff-7e0467c62428b3696cb555c69c52a4a0 I guess this is NYI so we can keep it open. I don't know if we have any alternative to the non-existing ｢.pid｣.

[perl #125580] [BUG] bag/set related issues

1. I think it is properly guarded now. (error message: Cannot coerce a lazy list onto a Bag) 2. That's OK. A lot of things require whitespace in 6lang (another example here: https://docs.6lang.org/language/traps#Less_than_vs._Word_quoting/Associative_indexing ). If you insist on no whitespace

[perl #125716] [LTA] error on typo

I guess this is not better, but it's progress: ===SORRY!=== Error while compiling -e Could not instantiate role 'A': Cannot invoke this object (REPR: Null; VMNull) at -e:1 On 2015-07-29 04:08:02, elizabeth wrote: > Please merge with #125716 or vice-versa :-) > > > On 29 Jul 2015, at 12:58,

[perl #125821] [LTA] error message when doing .rotate(Inf)

It is better now, but still LTA: This type cannot unbox to a native integer: P6opaque, Failure in block at -e line 1 On 2015-08-14 22:27:20, alex.jakime...@gmail.com wrote: > Code: > say .rotate(Inf); > > Result: > Earlier failures: > No zero-arg meaning for infix:<%> > in block at

[perl #125816] [9999] "x".indent(9999999999999999999999999999999999999999999999999)

Now it complains about unboxing a large int. On 2015-08-14 21:07:37, alex.jakime...@gmail.com wrote: > First part is OK, but once we start increasing the number it falls > apart. > > say "x".indent(9); > repeat count > 1073741824 arbitrarily unsupported... > in

[perl #125820] [9999] .roll(-9999999999999999999999999999999999999999999999999)

This now simply complains about unboxing a large integer. Not sure when this changed, but testneeded. On 2015-08-14 22:21:17, alex.jakime...@gmail.com wrote: > Code: > say e> .roll(-9).perl; > > Result: > it hangs > > Code: > say e> .roll(- > e>

[perl #126101] [BUG] 0.lotsof9s badly approximated

I think this is already fixed in https://github.com/rakudo/rakudo/commit/f6e25b54ea18ba7bd7d7861537d2439933000cb3 ¦f6e25b54ea18ba7bd7d78^: 1.83886070 Rat|999/1611392 True ¦f6e25b54ea18ba7bd7d78: 1

[perl #125336] Weird infinite ranges: Inf..0, -Inf..0 and NaN..0

I think that this stuff is resolved. Not sure when exactly because bisectable is refusing to work today, but this is TESTNEEDED. On 2015-06-05 09:18:44, alex.jakime...@gmail.com wrote: > Code: > .say for Inf..0 > > Result: > -9223372036854775808 > -9223372036854775808 > -9223372036854775808 >