They should be tested. They work by creating an anonymous role containing such methods, and mixing it into the metaclass instance for the class.

I have a tab with Raku/roast#553 opened for two years already. But there is always something with higher priority...

a tab with Raku/roast#553 opened for two years

I'm glad someone else uses their browser tabs as a TODO list 😃

I'm trying to figure out what'd be necessary to spec about metamethods? Aside of the evident:

class Foo { method ^foo(\obj) { ... } }
Foo.^foo;

We could spec for:

• obj to be the invocant (Foo in the above case, Foo.new with Foo.new.^foo, etc.)
• self to be a Metamodel::ClassHOW. At least this part of the metamodel is specced in Roast.
• no parameter needed if invoked as Foo.HOW.foo

And that's basically it. I wouldn't even spec the implementation detail of a role being mixed into HOW.

One behavior is certainly the candidate for Roast:

class C1 { method foo(\obj) { say "meta" } }
class C2 is C1 { }
C2.^foo; # meta

Not sure if many people know about this.