multi daft($x, $y) {...}
    class Foo {
        multi swip($self, $y: $z) {...}
    }

Is now:

    multi sub daft($x, $y) {...}
    class Foo {
        multi method swip($self, $y: $z) {...}
    }

I think this makes things even clearer, and has a fine-grained but
elegant control over the "scope" of the routine.

This easily allows for "multisubmethods" and even "multimacros"
(provided you have yourself a polymorphic object at compile time).

I also think it's important to say "multi" explicitly every time you
mean it.  It allows the compiler to warn you when you're just being
stupid about scoping as opposed to actually wanting to overload the
routine.  From a design perspective, it makes it clear that this method
introduces logical control-flow in addition to performing a task.

Luke