From @masak

<masak> disambiguating performs a narrowness analysis.
<masak> only things to the left of the ;; participate in it.
<jnthn> m​: multi a (;; Any $b) { say "one" }; multi a (;; Int $a) {
say "two" }; a(42)
<camelia> rakudo-moar 2bafa9​: OUTPUT«two␤»
<jnthn> I...think that one is a bug
<jnthn> We probably mis-handled initial ;;
<jnthn> That should be ambiguous
<masak> unless some other tiebreaking thing kicks in.
<jnthn> It shouldn't, I think we just don't handle initial ;; properly
<masak> m​: multi a ($b) { say "one" }; multi a ($a) { say "two" }; a(42)
<camelia> rakudo-moar 2bafa9​: OUTPUT«Ambiguous call to 'a'; these
signatures all match​:␤​:(Any $b)␤​:(Any $a)␤ [...]
<masak> that's the behavior I expect.
<jnthn> Right, same
* masak submits rakudobug

From @jnthn

On Thu Jun 25 04​:09​:04 2015, masak wrote​:

<masak> disambiguating performs a narrowness analysis.
<masak> only things to the left of the ;; participate in it.
<jnthn> m​: multi a (;; Any $b) { say "one" }; multi a (;; Int $a) {
say "two" }; a(42)
<camelia> rakudo-moar 2bafa9​: OUTPUT«two␤»
<jnthn> I...think that one is a bug
<jnthn> We probably mis-handled initial ;;
<jnthn> That should be ambiguous
<masak> unless some other tiebreaking thing kicks in.
<jnthn> It shouldn't, I think we just don't handle initial ;; properly
<masak> m​: multi a ($b) { say "one" }; multi a ($a) { say "two" }; a(42)
<camelia> rakudo-moar 2bafa9​: OUTPUT«Ambiguous call to 'a'; these
signatures all match​:␤​:(Any $b)␤​:(Any $a)␤ [...]
<masak> that's the behavior I expect.
<jnthn> Right, same
* masak submits rakudobug

Already fixed by lizmat++; added test to S06-multi/type-based.t.

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

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