Behaviour of `IMapper.Map(src, dst)` differs from AutoMapper

[AntiGuideAkquinet]

I discovered a difference between AutoMapper's and Mapster's implementation of the IMapper interface. Even though it could be argued that the AutoMapper behavior is unintuitive, I believe that for compatibility, Mapster should update the values of the destination object too.

AutoMapper

var output = mapper.Map(from, to);
// output and to contain the mapped values

Mapster

var output = mapper.Map(from, to);
// only output contains the mapped values

Risk
The risk that this issue poses is that usages like here do not map the value after switching to the Mapster implementation of IMapper