On Monday 02 October 2006 08:58, Jonathan Lang wrote: > I wonder if it would be worthwhile to extend the syntax of roles so > that you could prepend a "no" on any declarative line, resulting in a > compilation error any time something composing that role attempts to > include the feature in question. So, for instance, you might have > > role Bar { > no method baz (Num, Str); > } > > class Foo does Bar { > method baz (Num $n, Str $s) { ... } # compilation error: Bar > forbade this method! > }
This feels like the false-cognate problem waiting to creep back in. -- c