On Mon, 01 Feb 2016 21:59:33 -0800, alex.jakime...@gmail.com wrote:
> Let's try running the same code twice:
>
> m: my @x = ^10; my @y = @x.hyper(:3batch, :5degree).map: {
> sleep rand / 10; $_ + 1 }; say @y
> rakudo-moar a5fe34: OUTPUT«[]»
> m: my @x = ^10; my @y = @x.hyper(:3batch,
On Mon, 01 Feb 2016 21:59:33 -0800, alex.jakime...@gmail.com wrote:
> Let's try running the same code twice:
>
> m: my @x = ^10; my @y = @x.hyper(:3batch, :5degree).map: {
> sleep rand / 10; $_ + 1 }; say @y
> rakudo-moar a5fe34: OUTPUT«[]»
> m: my @x = ^10; my @y = @x.hyper(:3batch,
On Tue, 17 Jan 2017 10:10:44 -0800, coke wrote:
> The presence of a hyper or race causes incorrect output in some cases.
> Originally found with the .grep in the pipeline, but seems to impact
> even the simple case.
>
> $ perl6 -e 'say [+] (1..100)'
> 5050
>
> $ perl6 -e 'say [+] (1..100).race'
On Mon, 09 Nov 2015 06:36:49 -0800, matt.oa...@congenica.com wrote:
> The following has an empty result when using race or hyper in perl6
> version 2015.10-233-gac750a9 built on MoarVM version 2015.10-61-
> g624d504
>
> $ perl6
> > (1..10).grep(* > 3)
> (4 5 6 7 8 9 10)
> > (1..10).race().grep(*
On Mon, 09 Nov 2015 06:36:49 -0800, matt.oa...@congenica.com wrote:
> The following has an empty result when using race or hyper in perl6
> version 2015.10-233-gac750a9 built on MoarVM version 2015.10-61-
> g624d504
>
> $ perl6
> > (1..10).grep(* > 3)
> (4 5 6 7 8 9 10)
> > (1..10).race().grep(*
On Tue, 17 Jan 2017 10:10:44 -0800, coke wrote:
> The presence of a hyper or race causes incorrect output in some cases.
> Originally found with the .grep in the pipeline, but seems to impact
> even the simple case.
>
> $ perl6 -e 'say [+] (1..100)'
> 5050
>
> $ perl6 -e 'say [+] (1..100).race'
On Tue, 08 Aug 2017 18:40:48 -0700, alex.jakime...@gmail.com wrote:
> Code:
> for .hyper { say 2 }
>
> Result (2015.09-2015.06):
> 2
> 2
> 2
>
> Result (9b0b9effe5,2017.07,HEAD(6745517)):
> (no output)
>
>
> There seems to be nothing wrong with using a for loop on .hyper or
> .race, so it
On Tue, 08 Aug 2017 18:40:48 -0700, alex.jakime...@gmail.com wrote:
> Code:
> for .hyper { say 2 }
>
> Result (2015.09-2015.06):
> 2
> 2
> 2
>
> Result (9b0b9effe5,2017.07,HEAD(6745517)):
> (no output)
>
>
> There seems to be nothing wrong with using a for loop on .hyper or
> .race, so it
On Fri, 06 May 2016 08:37:20 -0700, sml...@gmail.com wrote:
> ➜ sub f ($a) { $a**2 }; say (^10).hyper.map().list;
> (0 1 4 9 16 25 36 49 64 81)
>
> ➜ multi f ($a) { $a**2 }; say (^10).hyper.map().list;
> ()
>
> The expected behavior would be for both examples to produce the same
>
On Thu, 08 Sep 2016 12:55:10 -0700, sml...@gmail.com wrote:
> If you `die` inside a `map/for` that is being `hyper/race`d...
>
> for (1..1).hyper { die }; sleep 1; say "Alive";
>
> ...it prints the exception's backtrace, but then resumes the program
> as if nothing had happened:
>
> Died
>
On Fri, 06 May 2016 08:37:20 -0700, sml...@gmail.com wrote:
> ➜ sub f ($a) { $a**2 }; say (^10).hyper.map().list;
> (0 1 4 9 16 25 36 49 64 81)
>
> ➜ multi f ($a) { $a**2 }; say (^10).hyper.map().list;
> ()
>
> The expected behavior would be for both examples to produce the same
>
On Thu, 08 Sep 2016 12:55:10 -0700, sml...@gmail.com wrote:
> If you `die` inside a `map/for` that is being `hyper/race`d...
>
> for (1..1).hyper { die }; sleep 1; say "Alive";
>
> ...it prints the exception's backtrace, but then resumes the program
> as if nothing had happened:
>
> Died
>
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 fixed as well, as the new method
> simply
> uses enum's `.value` to get the signal number:
>
> c:
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 fixed as well, as the new method
> simply
> uses enum's `.value` to get the signal number:
>
> c:
On 10/17/2017 09:27 PM, Timo Paulssen via RT wrote:
if you can, please re-compile MoarVM passing the same options that were
used before (you can find them on the first screenfuls of the Makefile
inside moarvm's source folder) to Configure.pl but also include
--debug=3 and --optimize=0. This is
On 10/17/2017 09:27 PM, Timo Paulssen via RT wrote:
> if you can, please re-compile MoarVM passing the same options that were
> used before (you can find them on the first screenfuls of the Makefile
> inside moarvm's source folder) to Configure.pl but also include
> --debug=3 and --optimize=0.
@Aleks-Daniel Jakimenko-Aleksejev
How can I reproduce this issue? What code did you use?
Well,
1) Install a mongod server and start it up. Its address might be
127.0.0.1:27017 which is the default for mongod servers. Servers can be
downloaded using
$ curl -O
@Aleks-Daniel Jakimenko-Aleksejev
> How can I reproduce this issue? What code did you use?
>
Well,
1) Install a mongod server and start it up. Its address might be
127.0.0.1:27017 which is the default for mongod servers. Servers can be
downloaded using
$ curl -O
18 matches
Mail list logo
