Coercion convention universal or not?

[doomvox]

(1) I don't understand quite what's being said here. Is the convention universally enforced? Is it only mandatory under certain circumstances?

(2) Is this section up-to-date? The general thrust is you need to monkey patch existing classes to add coercion methods for new types. Is that still true?

https://new-raku.finanalyst.org/language/signatures#Coercion_type

"Turning one type into another is done with coercion methods that have the same name as the target type. This convention is made mandatory by Signatures."

[coke]

Note: the official link to those docs is https://docs.raku.org/language/signatures#Coercion_type

[coke]

"Turning one type into another is done with coercion methods that have the same name as the target type. This convention is made mandatory by Signatures."

I can't find this text in the doc source or history.

[raiph]

@coke

FWIW, it's at https://docs.raku.org/language/typesystem#:~:text=Turning%20one%20type%20into%20another%20is%20done%20with%20coercion%20methods%20that%20have%20the%20same%20name%20as%20the%20target%20type

Imo this issue can be closed as a duplicate of (one aspect of the many covered by) #3807.

[coke]

Thanks for the report, added a note to the docs.