Tie-breaking rule between where-blocked multi and non-where-blocked multi is not specced about roast HOT 5 CLOSED

@zoffixznet
Thanks for merging my PR !

from roast.

However, it seems that there is another tie-breaking rule that where-blocked multi has higher priority than non-where-blocked multi.

Yes, and it's part of the test you quoted: https://github.com/perl6/roast/blob/master/S06-multi/subsignature.t#L437

it gets called when the argument is 1 and gives 1 as the result. The where-blocked multies take over for all the other values, because they're of a higher priority.

from roast.

@zoffixznet
Thanks for your reply !
I understand that, but I think we need another test case that implicitly explicitly shows the tie-breaking rule.
The test case defines a non-where-blocked multi routine first and a where-blocked multi routine second so that we can confirm Perl 6 call the second one first.

from roast.

The test case defines a non-where-blocked multi routine first and a where-blocked multi routine second so that we can confirm Perl 6 call the second one first.

Sure. Submit a PR with that test, please, if you can.

from roast.

ok. I've sent a PR.

from roast.