From @coke

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'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22)'
5028

$ perl6 -e 'say [+] (1..100).race.grep(* != 22)'
0

$ perl6 -e 'say [+] (1..100).hyper.grep(* != 22)'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22).race'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22).hyper'
0

--
Will "Coke" Coleda

From @zoffixznet

.elems also seems to always return 0​:

18​:11 brokenchicken m​: ^100 .race.elems.say
18​:11 camelia rakudo-moar 7d5bbe​: OUTPUT«0␤»
18​:11 brokenchicken m​: ^100 .race(​:batch).elems.say
18​:11 camelia rakudo-moar 7d5bbe​: OUTPUT«0␤»

From @smls

Looks like the same issue as

  #​127452​: [CONC] hyper is very broken, *sometimes* it returns nothing
  #​126597​: .race.grep(...) and .hyper.grep(...) produce an empty sequence

The RT System itself - Status changed from 'new' to 'open'

From @jnthn

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'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22)'
5028

$ perl6 -e 'say [+] (1..100).race.grep(* != 22)'
0

$ perl6 -e 'say [+] (1..100).hyper.grep(* != 22)'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22).race'
0

$ perl6 -e 'say [+] (1..100).grep(* != 22).hyper'
0

Fixed in new hyper/race implementation; tests in S07-hyperrace/hyper.t and S07-hyperrace/race.t.

@jnthn - Status changed from 'open' to 'resolved'