From @cjfields

Using tight OR for conditional tests is broken when chaining more than two tests (note second and forth test cases below). This is using rakudo (rev a16cde8), below is the version.

chris

Example code​:

cjfields$ perl6 -v
This compiler is built with the Parrot Compiler Toolkit, parrot revision 45127.
cjfields$ perl6

say 1 || 1
1
say 0 || 1
1
say 0 || 0 || 1
0
say 0 || 1 || 0 || 0
1

From @jnthn

On Tue Mar 23 10​:53​:37 2010, cjfields@​illinois.edu wrote​:

Using tight OR for conditional tests is broken when chaining more than
two tests (note second and forth test cases below). This is using
rakudo (rev a16cde8), below is the version.

chris

Example code​:

cjfields$ perl6 -v
This compiler is built with the Parrot Compiler Toolkit, parrot
revision 45127.
cjfields$ perl6

say 1 || 1
1
say 0 || 1
1
say 0 || 0 || 1
0
say 0 || 1 || 0 || 0
1

Youch, that's embarrassing! Fixed in d0bf6e3 and added a test.

Thanks,

Jonathan

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

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