The actor macro currently implements Into<#name> for #ty for each message type (#ty) in the message enum (#name), which enables converting from a specific message to the expected message enum.
From my point of view, implementing From<#ty> for #name would also implement the Into trait, but additionally serve more use cases, especially when working with generic message types, e.g. in such a case:
The actor macro currently implements
Into<#name> for #ty
for each message type (#ty
) in the message enum (#name
), which enables converting from a specific message to the expected message enum. From my point of view, implementingFrom<#ty> for #name
would also implement theInto
trait, but additionally serve more use cases, especially when working with generic message types, e.g. in such a case:Was there a specific reason for implementing
Into
instead ofFrom
?