Did a bit more experimenting, it seems to freeze only SOME of the time:
zoffix@VirtualBox:~$ perl6 -e 'react { whenever Supply.interval: 1 { say "Run
$_"; done } }'
Run 0
zoffix@VirtualBox:~$ perl6 -e 'react { whenever Supply.interval: 1 { say "Run
$_"; done } }'
Run 0
^C
zoffix@VirtualBox:~$
Skip-fudge added in https://github.com/perl6/roast/commit/a047d78ac9
Re-opening per TimToady's comments:
http://irclog.perlgeek.de/perl6/2016-07-21#i_12881470
The map de-lazifies when sunk, but in this case the for's sinking doesn't seem
to propagate to the map.
This, for example, prints all the values:
m: for ^3 { ^10 .map: *.say; Nil }; say 42;
--
Cheers,
I'm going to close this, since the original report was ruled as not a bug.
The lazines of such constructs has now also been documented in Traps.
--
Cheers,
ZZ | https://twitter.com/zoffix
Are you able to create those files manually? (e.g.
C:\Users\sinan\AppData\Local\Temp\rakudo\tempfile-spurt-test)
The `is` sub uses `eq` operator for comparison, which coerces items to Str.
So this ticket comes down to whether or not .Str on sets should sort their
elements. The problem with that is sets can contain different types of objects.
You could further put the argument that .Strs (or .gists) of
On Wed, 01 Feb 2017 09:03:37 -0800, rober...@semistable.com wrote:
> hi everyone,
>
> I have these two tiny pieces of code:
>
> ---8<-- server.p6 --
> my $listen = IO::Socket::INET.new(:listen, :localhost<127.0.0.1>,
> :localport());
> loop {
>
No idea if there's any relation between the two, but there's also this ticket
where a return type constraint set to Nil on a sub affects interpolation of a
code block in a string inside that sub; almost as if the constraint propagated
to it:
> But other close methods mention using a LEAVE
> phaser to avoid exceptions.
Would you be able to give a link where LEAVE is recommended?
$proc.err.close doesn't throw; it returns the Proc object. The throwage happens
when a Proc with non-zero exit status is **sunk**.
So instead of the LEAVE
On Sat, 28 Jan 2017 02:06:01 -0800, toolfor...@durchholz.org wrote:
> harness5 has --moar, which is used in makefiles, and I think the code
> also defines a --jvm.
> Neither --moar nor --jvm are reported with --help.
>
> The POD section in harness5 carries most options in its SYNOPIS, but
>
Closing, as the cause has been identified in previous replies.
Another report in NQP repo: https://github.com/perl6/nqp/issues/346
->8--
It is entirely possible that I am missing something obvious, but while trying
to figure out what happens between typing
C:\> perl6 -e "say 'yağmur'"
and getting the output
yagmur
All of the Range ~~ Range stuff is now fixed in
https://github.com/rakudo/rakudo/commit/8477f3b6b0
and tested in
https://github.com/perl6/roast/commit/e152a0ff3a37ef56c4c68af09421b47d5ad9d93c
https://github.com/perl6/roast/commit/3688301754e46a8b3afdbfad4e73c377e592e339
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/97359ae42e
Test unfudged in: https://github.com/perl6/roast/commit/b15e0a0d9b
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/97359ae42e
Test: https://github.com/perl6/roast/commit/1ed4d128d2
It's worth noting the fix is somewhat tangental to the original issue and the
issue isn't actually a bug.
What happens in the original
On Sat, 04 Feb 2017 16:36:21 -0800, jeff.lina...@gmail.com wrote:
> I type this into the REPL:
>
> loop (my $i = 10; $i > 0; $i--) { say $i; }
>
> It loops and then crashes:
>
> 10
> 9
> 8
> 7
> 6
> 5
> 4
> 3
> 2
> 1
> Type check failed in binding to $value; expected Any but got Mu (Mu)
> in
On Tue, 31 Jan 2017 18:58:22 -0800, pe...@mscha.org wrote:
> % perl6
> To exit type 'exit' or '^D'
> > my int $i = 10**16;
> 1
> > say $i;
> 1
> > say $i div 4;
> 468729856
> > say $i / 4;
> 2500
>
> This is on a 64-bit build, Rakudo Star 2017.01.
On Sun, 22 Jan 2017 09:43:51 -0800, sml...@gmail.com wrote:
> ➜ say (|() xx *)[0];
> Cannot shift from an empty Array
> in block at line 1
>
> Obviously, this golfed-down example is not useful as written. But this
> happened as an edge case of some real code I was writing.
>
>
On Sat, 21 Jan 2017 11:45:10 -0800, ale...@yahoo.com wrote:
> Take a look at the following examples - the second is more than
> 10x(!!!) faster:
> m: my int $i = 0; loop { if $i++ == 10_000_000 { last }}; say now -
> INIT now;rakudo-moar f97d5c: OUTPUT«2.0606382»
> m: my int $i = 0; loop { if
On Mon, 23 Jan 2017 01:02:07 -0800, alex.jakime...@gmail.com wrote:
> Code:
> grammar A { token TOP { }; token so { foo } }; say A.parse('foo')
>
> Result:
> Too many positionals passed; expected 1 argument but got 2
> in any !reduce at /tmp/whateverable/rakudo-
>
On Mon, 23 Jan 2017 01:37:16 -0800, alex.jakime...@gmail.com wrote:
> Code:
> class C { method defined { True } }; say ?C
>
> Result (2015.12,2016.02):
> True
>
> Result (2016.03,HEAD):
> False
>
>
>
> Bisectable points to
>
On Sat, 28 Jan 2017 02:10:47 -0800, toolfor...@durchholz.org wrote:
> I.e. it's copying perl6-m over perl6,
I assume that's to select which backend to use for testing. `perl6` is just a
1-line wrapper bash script.
That make target will also recompile the compiler if you made any changes to
it.
On Fri, 20 Jan 2017 09:16:18 -0800, mt1...@gmail.com wrote:
> Hi Will,
>
> How can it happen that a test gets hurt in this way? If I know this I
> could better search for the problem.
>
> Regards,
> Marcel
Hi,
Here's how that error happens:
The TAP protocol[^1] expects tests to be numbered
The original fix was reverted in
https://github.com/rakudo/rakudo/commit/121e5e32e9 per discussion
https://irclog.perlgeek.de/perl6-dev/2017-01-21#i_13962511
On Sat, 21 Jan 2017 13:52:37 -0800, ale...@yahoo.com wrote:
> m: my int $i = 0; while $i < 10_000_000 { $i++ }; say now - INIT
> now;rakudo-moar 7f245f: OUTPUT«5.1848902»
> m: my (int $i, int $nosink) = 0, 0; while $i < 10_000_000 { $nosink =
> $i++ }; say now - INIT now;rakudo-moar 7f245f:
On Fri, 20 Jan 2017 12:28:43 -0800, david.warring wrote:
> [09:20] bisect: sub clip-to ($min, $v is rw, $max) { $v =
> ($min
> max $v) min $max }; sub blah ( Array() :$rgbd ) { clip-to 0, $_, 255
> for
> @$rgbd; }; blah(rgbd => <.086, .165, .282> );
> [09:20] <+bisectable6> dwarring, Bisecting by
On Sun, 29 Jan 2017 01:56:16 -0800, j...@durchholz.org wrote:
> My approach to solving this would be to have make test use perl-m resp.
> perl-j directly.
OK. It already does so. As stated above, `make test` doesn't overwrite anything.
Closing.
Dupe of https://rt.perl.org/Ticket/Display.html?id=129248#ticket-history
including author and wording...
Accidental re-emailing?
Closing.
On Tue, 21 Feb 2017 05:15:56 -0800, jar...@bansu.fi wrote:
> EXAMPLE:
> my %hash = foo => 1;
> if %hash:exists {
> say "not gonna print this";
> }
> my $key = 'b';
> if %hash«$key»:exists {
> say "why i'm here";
> }
>
> OUTPUT:
> why i'm here
>
> EXPECTED RESULT:
> (Should not print anything)
>
On Wed, 22 Feb 2017 19:32:31 -0800, comdog wrote:
> Here's a curious change over in precision:
>
> > 4.999 ~~ 0..^5
> True
> > 4. ~~ 0..^5
> False
>
> I figure this is an implementation detail that ties to storage, but
> one of the selling points of
On Thu, 23 Feb 2017 22:01:25 -0800, j...@durchholz.org wrote:
> Somewhat offtopic:
Feels like a bad place for offtopic discussions. You can ask questions in the
same IRC channel you evaled your example.
> toolforger: p6: say Inf cmp Inf
> camelia: rakudo-moar 320c2f: OUTPUT: «Same»
>
> I.e.
On Mon, 13 Feb 2017 21:04:37 -0800, raiph wrote:
> This comment is technically redundant. And maybe not helpful. I
> apologize if it's annoying to anyone.
Not annoying, but I feel we all have thoroughly confused bdfoy by now :P
Some minor corrections:
> 4.1 `sink some.expression;`
>
> In stark
On Sat, 11 Feb 2017 03:29:18 -0800, moritz wrote:
> sub f($x) {
> sub {
> if True {
> say &?ROUTINE.name
> }
> }
> }.(42)()
>
> This prints f on Rakudo 2017.01-170-gc0a907f built on MoarVM version
> 2017.01-31-g20dfa6b
>
> &?ROUTINE
On Tue, 27 Dec 2016 11:02:17 -0800, c...@zoffix.com wrote:
> In this code, I would've expected the second multi to be used, since
> I'm not providing
> any named args. I'm fuzzy on whether named params affect multi
> dispatch, but even if they
> wouldn't the multi without any named params is later
I found where the LEAVE was mentioned and removed it.
The .close you're calling is actually from IO::Pipe, not IO::Handle.
Probably something else should be clarified in the docs to avoid that sort of
confusion as well.
Marked it as TODO for my IO grant thing and will resolve this ticket as
On Sat, 09 Jan 2016 05:05:06 -0800, lucasbuchala wrote:
> An itemized empty list is getting ".perl"-stringified as "$()", which
> I think is wrong since $() means some idiom using "$/". The fix should
> be just to make it stringify as "$( )" (with a space in the middle) or
> maybe "().item" for
On Thu, 09 Feb 2017 16:51:00 -0800, samant...@posteo.net wrote:
> > 1.1.base(1)
> Attempt to divide 2.30258509299405 by zero using /
> in block at line 1
>
> Fudged roast test in S32-num/base.t
Thank you for the report. This is now fixed.
Fix:
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote:
> $ echo %windir%
> C:\WINDOWS
>
> $ echo %WINDIR%
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> (Any)
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -v
> This is
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote:
> $ echo %windir%
> C:\WINDOWS
>
> $ echo %WINDIR%
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> (Any)
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -v
> This is
Just realized something: I fixed Str ~~ Numeric to not throw, so on HEAD there
won't be any Failures at all with the sample code.
I tried changing the tests to use $a + $b instead of $a ~~ $b, but then the
DESTROY warning does not occur...
... should this ticket be closed?
On Sat, 28 Jan 2017 16:42:46 -0800, mt1...@gmail.com wrote:
> Hi,
>
> I get the following error using version 2016.08.1-66-g1ff1aae built on
> MoarVM version 2016.08
> implementing Perl 6.c.
>
> Cannot resolve caller BUILD(CC+{RR}: ); none of these signatures match:
> (CC $: Str :$t!, *%_)
On Sat, 03 Sep 2016 21:03:12 -0700, c...@zoffix.com wrote:
> To add, the cause is .is-lazy on slurpy args seems to attempt to reify
> the entire sequence:
>
> -> *@a { @a.is-lazy.say }(1…∞) # hangs
The rotor hang fixed in https://github.com/rakudo/rakudo/commit/d7b82149d31da0
The slurpy hang
On Mon, 06 Feb 2017 04:04:16 -0800, consult...@jnthn.net wrote:
> Discovered this after some $dayjob code got busted by updating Rakudo.
> After bisecting, I got it down to this commit:
>
> https://github.com/rakudo/rakudo/commit/fd8df7f2ad509689a64b8825e1c4bb622cf7486f
>
> And from that
Thank you for the report. This is now fixed:
Rakudo fix:
https://github.com/rakudo/rakudo/commit/dc69dafc42
https://github.com/rakudo/rakudo/commit/11d005e605
https://github.com/rakudo/rakudo/commit/4b85db6e8c
Tests:
https://github.com/perl6/roast/commit/a460cdc7ac
Looks like several other tests in S17-procasync/basic.t would be failing as
well if it weren't for the explicit kludges[^1][^2] added to replace "\r\n" to
"\n". And `grep -nFR '\r\n' | grep subs` shows[^3] 32 potential places with a
similar workaround.
Pretty LTA for portable Perl 6 code to
On Tue, 17 Jan 2017 08:08:34 -0800, cookbook_...@yahoo.co.jp wrote:
> On Tue, 17 Jan 2017 06:08:04 -0800, c...@zoffix.com wrote:
> > Can you please include code that actually reproduces the problem?
>
> I'm very sorry. I can't remember exactly how to generate this error, I
> just remember is that
One more data point:
reversing the load order prevents the segfault (that is, doing use A; use B;
instead of use B; use A)
Can you please include code that actually reproduces the problem?
On Thu, 19 Jan 2017 18:10:27 -0800, alex.jakime...@gmail.com wrote:
> I guess it is supposed to work?
Isn't this the case where HyperWhatever is used as a term by itself, so you're
passing it itself to [+] metaop and doesn't curry and hence its complaining.
Same's with regular Whatever:
m:
On Mon, 27 Feb 2017 14:35:17 -0800, zef...@fysh.org wrote:
> > try { my Int $a; $a = "foo" }; say ?$!.backtrace; say
> > ?$!.perl.EVAL.backtrace
> True
> False
>
> .perl.EVAL is failing to round-trip the exception object, as
> demonstrated
> by the differing truthiness of the value returned by
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/76f71878da
Test: https://github.com/perl6/roast/commit/908348eef1
Sorry, wrong example of failure mode. It seems to happen in `while`:
m: while $++ < 5 { when {True} {Failure.new} }
rakudo-moar 9d497e: ( no output )
I went to write a test for this, but can't repoduce the issue. I tried a
handful of releases with the IRC bot, then built 2016.01 release and the
mentioned 86a90be commit, but none of them fail.
Perhaps this is an OSX-only issue? Could someone with OSX try reproing it on
86a90be commit and if
FWIW, this bug makes at least mild exploitation possible, depending on how the
program validates input:
Setup: dir and input check to ensure user-supplied path is not outside of it:
13:41 IOninja m: "/tmp/root/tmp".IO.mkdir;
"/tmp/root/secret.txt".IO.spurt: 'p4sswrd';
On Mon, 27 Feb 2017 00:21:17 -0800, zef...@fysh.org wrote:
> > say "a"; "a" + 2; say "b"
> a
> > "a" + 2
> Cannot convert string to number: base-10 number must begin with valid
> digits or '.' in '^a' (indicated by ^)
> in block at line 1
>
> In both of these cases the addition signals an
On Mon, 27 Feb 2017 14:27:04 -0800, zef...@fysh.org wrote:
> Zoffix Znet via RT wrote:
> >Fix: https://github.com/rakudo/rakudo/commit/db70a1fda8
>
> This doesn't distinguish between an exception being thrown and the
> expression evaluating to an exception object. The
On Tue Aug 23 11:35:55 2016, coke wrote:
> This is no longer an issue in at least 2016.07.1
>
> Closable with tests.
The issue is still present in current bleed (2016.08.1-73-gfbeadbf)
> On Thu Jan 14 03:33:28 2016, nadim.khe...@gmail.com wrote:
> > $?FILE is the path and file name
> >
> >
Fixed in https://github.com/rakudo/rakudo/commit/b508576fc5
Tests added in https://github.com/perl6/roast/commit/dedfdf91e7
Fixed in: https://github.com/rakudo/rakudo/commit/75ba8cc6c3
Tests: https://github.com/perl6/roast/commit/350d02be0b
Fixed in
https://github.com/rakudo/rakudo/commit/490cf728e6396dd99e10ab633f33e4df8cb35a52
Tests added in
https://github.com/perl6/roast/commit/09c8d3fd7af5b01d79dda46e462e9ae46fa5f365
Thanks for the report.
Fixed in https://github.com/rakudo/rakudo/commit/a2b6f74be1
Tests added in https://github.com/perl6/roast/commit/3ed2af4c42
Not a bug.
See also http://irclog.perlgeek.de/perl6-dev/2016-09-08#i_13170729
Happens with 'S' and possibly some other ops. The missing bit is the
`$.operator`, which is obtained from `$op`
$ ./perl6 -e '1 S?? 2 !! 3'
===SORRY!=== Error while compiling -e
Cannot sequence the args of because conditional operators are too fiddly
at -e:1
--> 1 S?? 2 !!⏏ 3
The issue is due to there being a multi new [^1] that takes a Real min value
and *coerces* the max value to a real. So in the case described in this ticket,
it will coerce the Str max to Int, and by the time we get to .rand, both args
are Ints.
As suggested on IRC [^2], we can try removing
Thanks for the report.
The issue has now been fixed in
https://github.com/rakudo/rakudo/commit/77d9d41fc4
(Tests added in the same commit).
On Tue Aug 30 11:46:53 2016, sml...@gmail.com wrote:
> The trap comes from the fact that `..` and `...` with a Str endpoint
> *don't* use .succ/.pred:
>
> "35".."40" # does something weird (and IMO useless) that is different
> from .succ
Agreed, that's weird. I'm unsure why it's counting down
Attached 'backtrace-original.txt' is the output from the added CATCH and
--ll-exception.
I was able to golf it down to this:
await do for 3¹²³⁴⁵ … 3¹²³⁴⁵+127 -> $num {
start $num.is-prime ?? "$num is prime" !! "$num is not prime";;
}
CATCH { .backtrace.full.say }
And that backtrace
On Sun Sep 11 13:48:04 2016, tbrowder wrote:
> Both routines need an alias (or adverb) so that a newline is
> automatically appended to the output. I would like to see something
> like:
>
> sprintfn
> printfn
I'd prefer to avoid adding two new subs and two new methods for the sake of
saving a
Fixed in https://github.com/rakudo/rakudo/commit/2287173ef2
Tests unfudged in https://github.com/perl6/roast/commit/addcec6732
On Sun Sep 11 07:01:11 2016, pierre.vig...@gmail.com wrote:
> Hi,
>
> i stumbled a across a strange behaviour when playing with Supplier, i
> tried to gulf it down, starting from the documentation of supply. The
> following code, taken from the documentation and slightly modified is
> working as
Fudging tests and reopening as the issue appears to still exist on OSX:
http://irclog.perlgeek.de/perl6-dev/2016-09-11#i_13187953
Fudged tests added in https://github.com/perl6/roast/commit/02d698835e
Still segfaults about once in 10 runs on 2016.08.1-145-g87f772e
Thanks for the report.
Fixed in NQP: https://github.com/perl6/nqp/commit/32fd43da48
Fixed in Rakudo: https://github.com/rakudo/rakudo/commit/87f772ee53
Tests added in https://github.com/perl6/roast/commit/9650cd258f
On Sun Jul 31 08:06:08 2016, gfldex wrote:
> m: say Q ⸨oi!⸩
> #
I'm unable to reproduce this on HEAD Rakudo even with $n set to 40 and
RAKUDO_MAX_THREADS set to 50.
What is your perl6 version (perl6 -v). Are you able to try this against HEAD
[^1]? Yesterday a fix went in addressing issues in sockets and threads; and
recently there have been many other
Thanks for the report.
It appears all of .split's adverbs were broken on Cool, including the
.split(@needles) call form.
Fixed in https://github.com/rakudo/rakudo/commit/b771bcc97a
Tests added in https://github.com/perl6/roast/commit/060cf7abff
On Sat Sep 10 09:01:27 2016,
Thanks for the report!
Unfortunately the fix you provided is a no-op, because empty arrays are falsy,
so the check doesn't add anything extra.
The issue was the nextsame candidate was the one with the slurpy that called
the current candidate back again, resulting in an infiniloop.
The issue
On Mon Sep 12 07:33:33 2016, darek.cidlin...@atlas.cz wrote:
> 2) should the newline before the ... operator be forbidden,
> the error message could be clearer than a single asterisk.
Thanks for the report, but I think I'm going to close this without any changes.
What happens is your }
For others reading the ticket. I asked OP to submit the fix[^1] to get some
practice fixing Rakudo bugs, so this ticket is taken.
[1] http://irclog.perlgeek.de/perl6/2016-09-12#i_13194275
On Wed Sep 21 19:37:06 2016, ddgr...@gmail.com wrote:
> Test added in https://github.com/perl6/roast/commit/6cc1a85cf4
This ticket still needs tests for Windows.
Fixed in https://github.com/rakudo/rakudo/commit/8f2279b155
Tests added in https://github.com/perl6/roast/commit/816b913d98
On Thu Aug 27 04:25:26 2015, masak wrote:
> m: my %b := BagHash.new(); %b.classify-list( {.comb}, 20..40
> ); say %b.perl
> rakudo-moar a46b09: OUTPUT«postcircumfix:<{ }>
Posting on behalf of dogbert17:
I believe that I have encountered the same bug under different circumstances.
With the help of hackedNODE and others on #perl6
it seems as if the problem described below also suffers from the wrong multi
candidate being called. In
First a bit of deconfusion: negative exponents just mean x⁻² = 1/x². That works
just fine and is not relevant to this ticket:
m: say (-2) ** -2
rakudo-moar 605f27: OUTPUT«0.25»
Fractional exponents mean the number is raised to the power of the numerator
and then the
First a bit of deconfusion: negative exponents just mean x⁻² = 1/x². That works
just fine and is not relevant to this ticket:
m: say (-2) ** -2
rakudo-moar 605f27: OUTPUT«0.25»
Fractional exponents mean the number is raised to the power of the numerator
and then the
Fixed in https://github.com/rakudo/rakudo/commit/d63f983290
Tests added in https://github.com/perl6/roast/commit/0ade2a58c9
On Fri Jan 29 06:50:08 2016, pawel.pab...@getresponse.com wrote:
> multi sub infix:<==> (Int $a, Str $b) { $a == $b }
>
> Will never finish compilation on Rakudo 6.c and causes severe memory
> leak. I found that:
>
> 1. Types must be different in signature
> (Int $a, Str $b) # hangs
> (Str $a,
I'm not seeing the bug here, to be honest.
The `Body` is asking for one or more tokens `Text`, *nothing* is a valid match
for those tokens, so after matching the provided text, your grammar continues
to match nothing infinite number of times.
On Tue Sep 20 13:54:33 2016, jan-olof.hen...@bredband.net wrote:
> # tested with
>
> dogbert@dogbert-VirtualBox ~ $ perl6 -v
> This is Rakudo version 2016.09-19-g8be36b1 built on MoarVM version 2016.09
> implementing Perl 6.c
>
> # the following two examples behave quite differently
>
>
Here's a much shorter way to reproduce it:
perl6 -e '"foo" ~~ /(.*)+/' # hangs
While my previous explanation for why this occurs makes sense, it's worth
noting this behaviour is not observed in Perl 5, for example:
perl -e '"foo" =~ /(.*)+/' # does not hang
This now appears to have been fixed by some of the recent async fixes.
Tests now pass and have been unfudged in
https://github.com/perl6/roast/commit/92951b39ee
This now appears to have been fixed by some of the recent async fixes.
Tests now pass and have been unfudged in
https://github.com/perl6/roast/commit/92951b39ee
Fixed in https://github.com/rakudo/rakudo/commit/f6524e61e8
Tests added in https://github.com/perl6/roast/commit/391ecba7b9
On Wed Sep 28 06:02:48 2016, c...@zoffix.com wrote:
> # I have the fix; filing for records
>
> The .subst-mutate routine returns a Match object (or Nil) on singular
>
Seems the issue has more to do with running an empty loop, rather than
performing a real computation.
This is a run on a 4-core box. Attempting to parallelize an empty loop makes
the execution 1 second slower:
my = { for ^2_000_000 { } };
my $start = now; (^4).map: my $stop = now;
Seems to be fixed in latest Rakudo, per
http://irclog.perlgeek.de/perl6/2016-09-26#i_13283196
Tests needed.
Fixed in https://github.com/rakudo/rakudo/commit/6ef4cdf543
Tests added in https://github.com/perl6/roast/commit/925cf4bd8b
On Tue Sep 27 11:39:00 2016, c...@zoffix.com wrote:
> # I have the fix; filing for records
>
> The .subst/.subst-mutate methods slurp several of their options into a
>
Fixed in https://github.com/rakudo/rakudo/commit/28bf87439e
Tests in https://github.com/perl6/roast/commit/3253db362c
On Fri Sep 30 23:14:32 2016, c...@zoffix.com wrote:
> # I have the fix; filing for records
>
> m: [].splice: 0, [] # w
> rakudo-moar 1f29cb:
The original fix was not enough, as passing incorrect type to `offset` also has
the same issue.
Not pretty, but this commit fixes that issue:
https://github.com/rakudo/rakudo/commit/b77d2b71db
And tests for offset condition hang added in
https://github.com/perl6/roast/commit/5d8750321d
On
Looks like libtommath has now been fixed:
https://github.com/libtom/libtommath/pull/57
On Sat Oct 08 14:47:40 2016, timo wrote:
> Apparently libtommath is known to leave some bits 0 when specific
> conditions for the defines are met; i haven't looked but i suspect we
> are hitting exactly this
Fixed in https://github.com/rakudo/rakudo/commit/3b5ef07cee
Tests added in
https://github.com/perl6/roast/blob/412539ab809a769b7bf36df02c4aba8040f95f7e/S04-exceptions/exceptions-json.t#L27
On Wed Oct 05 11:07:23 2016, nxadm wrote:
> Hi,
>
> Great job adding JSON error output (lizmat++). This
There's another couple of LTA errors for this, such us when a stubbed class is
attempted to be `does` with or when a stubbed role is `does` with before it's
defined:
m: class A { ... }; class B does A { }; class A { }
rakudo-moar a581bf: OUTPUT«Unhandled exception: No such method 'item'
for
On Tue, 08 Nov 2016 06:31:15 -0800, c...@fastmail.co.uk wrote:
> Pull requests raised for discussion:
>
> https://github.com/rakudo/rakudo/pull/915
> https://github.com/perl6/roast/pull/180
Merged. Thanks.
1 - 100 of 987 matches
Mail list logo
