Support inheritance in which all classes are monitors

[japhb]

In other words, support:

monitor A      { method foo {} }
monitor B is A { method bar {} }

... and have foo and bar be mutually excluded.

[lizmat]

I'm not seeing this happening with OO::Monitors, but maybe it would be possible with Method::Protected. Something like:

class A is B {
    method foo() is protected(B) { ... }
}

where B must be a parent A ?

[japhb]

I'm not seeing this happening with OO::Monitors,

Do you mean that OO::Monitors can't support this given its current design, or just that nobody is likely to work on it?

but maybe it would be possible with Method::Protected. Something like:

class A is B {
method foo() is protected(B) { ... }
}

where B must be a parent A ?

Not a bad idea, though I note that Method::Protected already knows to look for a $!LOCK attribute (and then access it via accessor method); perhaps it could simply look through the MRO for that attribute instead of checking only the current package?

[lizmat]

perhaps it could simply look through the MRO for that attribute instead of checking only the current package?

This is in fact what already happens, I now realize, because .^attributes does this by default:

class A { has $!a }
class B is A {
    method b() { say self.^attributes[0].name }
}
B.b;  # $!a

Now I wonder whether this is a bug or a feature.