From @masak

<masak> rakudo​: say "!$_!" for 1.trans((1..26) => (14..26,1..13)),
2.trans((1..26) => (14..26,1..13))
<p6eval> rakudo 184bf7​: OUTPUT«!14!␤!15!␤»
<masak> rakudo​: say "!$_!" for (1, 2)>>.trans((1..26) => (14..26,1..13))
<p6eval> rakudo 184bf7​: OUTPUT«!14!␤!!␤»
* masak submits rakudobug
<masak> hm, this would be handled by !dispatch_dispatcher_parallel in
src/glue/dispatch.pir ...
<masak> it looks like perfectly innocent PIR code.
<masak> "I notice that I am confused."
<masak> doing the calls one after the other gives the desired result.
doing the calls one after the other using the
postfix_prefix_metaoperator Texas thingy doesn't give the desired
result. there's nothing obviously wrong with the code that handles the
dispatch.
* masak broods
<masak> rakudo​: say "!$_!" for (1, 2)>>.trans([1..26] => [14..26,1..13])
<p6eval> rakudo 184bf7​: OUTPUT«!14!␤!15!␤»
<masak> could this be -- *gasp* -- an iterator-related bug?
<jnthn> duh duh DUUUHHH!

From @timo

Added a test case in Raku/roast@b5ce7a2

The bug appears to be fixed, so closing.

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

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