It looks like even if I declare the move constructor explicitly, it doesn't help with the overload resolution. However, if I call std::move when invoking the constructor, it will choose the move constructor regardless of whether it is declared explicitly. While there is no change necessary, if you'd like the new unit test that demonstrates the workaround, feel free to merge it.
It looks like even if I declare the move constructor explicitly, it doesn't help with the overload resolution. However, if I call
std::move
when invoking the constructor, it will choose the move constructor regardless of whether it is declared explicitly. While there is no change necessary, if you'd like the new unit test that demonstrates the workaround, feel free to merge it.33