Get Better error message that "is trait on $-sigil variable not yet implemented. Sorry."?

I just tried: > my $x is Int = 42; ===SORRY!=== Error while compiling: is trait on $-sigil variable not yet implemented. Sorry. --> my $x is Int⏏ = 42; expecting any of: constraint and was a bit disappointed. It took me a while and reading the book of Andrew Shitov till I tried

Re: Compiling Rakudo in parallel

On 26 May 2017 at 07:04, Gabor Szabo wrote: > Would someone update the README that comes with Rakudo Star with this > information, please? I don't see any point since I think he is basically saying it's not worth trying to compile in parallel -- the bits which compile slowly can't be compiled in

Re: Get Better error message that "is trait on $-sigil variable not yet implemented. Sorry."?

To file a bug in Rakudo, you should email rakudo...@perl.org. If it's a better error message you want, put "LTA Error" in the email subject somewhere. LTA means "less than awesome", because we in Perl 6 land only accept awesome error messages. If you want to actually have the feature, put "[NYI]

Re: [perl #131362] [LTA] Can “Cannot modify an immutable X” error message also include the value? (42 = $x)

Fixed with https://github.com/rakudo/rakudo/commit/25d0430ab0 , tests needed. > On 25 May 2017, at 14:48, Aleks-Daniel Jakimenko-Aleksejev (via RT) > wrote: > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #131362] > # in the subject line of a

Re: Get Better error message that "is trait on $-sigil variable not yet implemented. Sorry."?

Fixed with https://github.com/rakudo/rakudo/commit/f2fca0c8c2 . > On 26 May 2017, at 10:47, Brent Laabs wrote: > > To file a bug in Rakudo, you should email rakudo...@perl.org. > > If it's a better error message you want, put "LTA Error" in the email subject > somewhere. LTA means "less than

[perl #126598] [IO] With chomping active, we lose a last empty line

On Mon, 09 Nov 2015 07:14:47 -0800, elizabeth wrote: > $ 6 spurt("bar","\n"); dd open("bar").get > Str $var = Str # should be "" > > $ 6 'spurt("bar","\n"); dd open("bar",:!chomp).get' > Str $var = "\n" > Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compa

[perl #126598] [IO] With chomping active, we lose a last empty line

On Mon, 09 Nov 2015 07:14:47 -0800, elizabeth wrote: > $ 6 spurt("bar","\n"); dd open("bar").get > Str $var = Str # should be "" > > $ 6 'spurt("bar","\n"); dd open("bar",:!chomp).get' > Str $var = "\n" > Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compa

[perl #125079] Roast rakudo skip/todo test:./S16-filehandles/io.t line:287 reason: 'Too late to change filehandle encoding'

Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compare/f2fca0c8c2...41bb13722c Test: (unfudged) https://github.com/perl6/roast/commit/39d6cd9cea

[perl #125079] Roast rakudo skip/todo test:./S16-filehandles/io.t line:287 reason: 'Too late to change filehandle encoding'

Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compare/f2fca0c8c2...41bb13722c Test: (unfudged) https://github.com/perl6/roast/commit/39d6cd9cea

[perl #125082] Roast rakudo skip/todo test:./S16-filehandles/io.t line:296 reason: 'Will fail due to above failure'

Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compare/f2fca0c8c2...41bb13722c Test: (unfudged) https://github.com/perl6/roast/commit/39d6cd9cea

[perl #125082] Roast rakudo skip/todo test:./S16-filehandles/io.t line:296 reason: 'Will fail due to above failure'

Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/compare/f2fca0c8c2...41bb13722c Test: (unfudged) https://github.com/perl6/roast/commit/39d6cd9cea

Re: Are sigils required?

Isn't it stretching the definition of "variable" to use it for what are really user-named constants? On 5/26/17, Gabor Szabo wrote: > thanks! > > > Gabor "impatient" Szabo > > On Fri, May 26, 2017 at 9:27 AM, Brent Laabs wrote: >> You didn't keep reading far enough. >> >>> For information on var

Re: Are sigils required?

You can bind an explicitly created scalar into a sigil-less variable and it'll be variable rather than constant

Re: Task::Star and Panda

On Wed, May 24, 2017 at 12:27 AM, ToddAndMargo wrote: > On 05/23/2017 07:44 PM, Richard Hainsworth wrote: >> >> The issue is not poor quality software! >> >> The problem is community management. > > > You have a point. I think the lack of interest is > because they have decided to use zef ins

Re: Are sigils required?

That sounds like a rather complicated way to render a program even more confusing. On 5/26/17, Timo Paulssen wrote: > You can bind an explicitly created scalar into a sigil-less variable and > it'll be variable rather than constant >

Re: Task::Star and Panda

On Thu, May 25, 2017 at 5:12 AM, Gabor Szabo wrote: > On Thu, May 25, 2017 at 11:59 AM, Richard Hainsworth > wrote: > >> However, for someone new to the Perl6 world, there needs to be some form of >> recommendation about useful "first" modules. > > Agree, but would go further: > > Someone new to

How to upgrade a module?

Hi there, So I have been working on Bailador and pushing out changes lately. How can I tell zef to upgrade it? I ran zef update zef install --force Bailador it installed Bailador again, but it was not the most recent code from GitHub. I tried zef upgrade Bailador It told me ===> Searching f

Re: Task::Star and Panda

On 05/26/2017 07:28 PM, Will Coleda wrote: > Again, panda is not actually broken. Sounds like it was missing in a > travis > config, but that isn't an issue with panda, per se. It's that almost all travis configs start with "rakudobrew build panda" which now dies, so immediately a whole bunch of m

[perl #131375] [BUG] error initializing large array on Windows (64-bit)

# New Ticket Created by Michael Schaap # Please include the string: [perl #131375] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131375 > The following script: #!/usr/bin/env perl6 use v6.c; sub MAIN(Int $n

[perl #131376] [IO][REGRESSION] read on IO handle following SeekFromCurrent

# New Ticket Created by David Warring # Please include the string: [perl #131376] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131376 > 3 more elements. Show/hide. 19:01

[perl #131376] [IO][REGRESSION] read on IO handle following SeekFromCurrent

Bisectable failed in the provided log, here is the right result: AlexDaniel, Bisecting by output (old=2015.12 new=95b4e5d) because on both starting points the exit code is 0 AlexDaniel, bisect log: https://gist.github.com/1b6f1bdabefa1cb13338451abceea153 AlexDaniel, (2017-05-25) https://github

[perl #131376] [IO][REGRESSION] read on IO handle following SeekFromCurrent

On Fri, 26 May 2017 12:14:13 -0700, david.warring wrote: > 3 more elements. Show/hide. > 19:01 > dwarring p6: > "tst.txt".IO.spurt([~] 'a' .. 'z'); my $ioh = "tst.txt".IO.open(:r); > say > $ioh.read(4); $ioh.seek(1, SeekFromCurrent); say $ioh

[perl #131376] [IO][REGRESSION] read on IO handle following SeekFromCurrent

On Fri, 26 May 2017 12:14:13 -0700, david.warring wrote: > 3 more elements. Show/hide. > 19:01 > dwarring p6: > "tst.txt".IO.spurt([~] 'a' .. 'z'); my $ioh = "tst.txt".IO.open(:r); > say > $ioh.read(4); $ioh.seek(1, SeekFromCurrent); say $ioh

[perl #131375] [BUG] error initializing large array on Windows (64-bit)

On Fri, 26 May 2017 11:58:50 -0700, pe...@mscha.org wrote: > The following script: > > #!/usr/bin/env perl6 > > use v6.c; > > sub MAIN(Int $n = 20_000_000) > { > say "Starting..."; > my int @a = 1..$n; > say "Array initialized."; > sleep 10

[perl #131375] [BUG] error initializing large array on Windows (64-bit)

On Fri, 26 May 2017 11:58:50 -0700, pe...@mscha.org wrote: > The following script: > > #!/usr/bin/env perl6 > > use v6.c; > > sub MAIN(Int $n = 20_000_000) > { > say "Starting..."; > my int @a = 1..$n; > say "Array initialized."; > sleep 10

[perl #131378] 2017.05-133-g094e77a fails to gmake install on Windows10

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131378] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131378 > All proceeds well until install-core-dist.pl at which point it crashes with rename operat

[perl #131379] [IO] read from file containing 1-char of malformed UTF returns empty string

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131379] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131379 > This seem to have existed for a while and isn't due to encoding refactor. 01:24 c: 2017

[perl6/specs] 5c9262: Uniquify headlines in S22 to work around a renderi...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5c9262e200a74d5f553684532143568ceda89ba8 https://github.com/perl6/specs/commit/5c9262e200a74d5f553684532143568ceda89ba8 Author: Stefan Seifert Date: 2017-05-26 (Fri, 26 May 2017) Changed paths: M S22

[perl #131364] concurrent quicksort from Damien gives different crashes each time

# New Ticket Created by Sverre Eldøy # Please include the string: [perl #131364] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131364 > Hi! I was just playing around with the concurrent quicksort thing that Damien made.. It

[perl #131372] [BUG] infix eqv may hang when comparing equivalent recursive arrays

# 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/Display.html?id=131372 > This is Rakudo version 2017.04.3 built on MoarVM version 2017.04-53-g

[perl #131378] 2017.05-133-g094e77a fails to gmake install on Windows10

I bet, there's a file handle left open somewhere. This error is about CompUnit::Repository::Staging which is precompiled _three times_ in that script. Once when loading the module, the second time when installing the CORE dist and the third time to fix the source path of the installed Staging mo