When deep-copying messages for in-process RPCs, the logic did not support the case where the source or destination was a dynamic message but not both. It would check that the two had the same concrete type and fail in the event that one was a generated message type and the other was a *dynamic.Message.
This amends that, which allows using an inprocgrpc.Channel with a dynamic client.
When deep-copying messages for in-process RPCs, the logic did not support the case where the source or destination was a dynamic message but not both. It would check that the two had the same concrete type and fail in the event that one was a generated message type and the other was a
*dynamic.Message.This amends that, which allows using an
inprocgrpc.Channelwith a dynamic client.