Document Metamodel::TypePretense and Metamodel::MethodDelegation #3352
Conversation
doc/Type/Metamodel/CoercionHOW.pod6
Outdated
|
|
||
| In signatures, I<type coercions> may be used to change the types of | ||
| arguments or return values from one type to another: | ||
|
|
There was a problem hiding this comment.
Maybe link the corresponding explanation?
doc/Type/Metamodel/CoercionHOW.pod6
Outdated
| Coercions L<pretend to be|/type/Metamodel::TypePretense> of types C<Any> | ||
| and C<Mu>, and L<delegate|/type/Metamodel::MethodDelegation> methods to | ||
| C<Any>. | ||
|
|
There was a problem hiding this comment.
Maybe provide an use case for this?
|
|
Yes that would be fine; maybe create a ticket to track any remaining work. |
|
Of the three, only Metamodel::CoercionHOW seems to be spec'd. |
Kaiepi
force-pushed
the
metamodel-coercionhow
branch
from
7e55d2e to
7f6f2c7
Compare
|
|
Kaiepi
changed the title
The problem
Metamodel::TypePretense,Metamodel::MethodDelegation, andMetamodel::CoercionHOWare undocumented. While documentation for the latter isn't terribly important IMO, the former two are very useful when implementing your own HOWs and really need documentation. Documenting them also helps explain some behaviours of roles that may not be entirely clear.Solution provided
Document the metaroles and metaclasses mentioned, and update roles' HOWs' documentation.