In playing with undefined behavior sanitizer I learned that it is undefined behavior to pass a nullptr to std::memcpy even if the count/size argument is 0, see https://en.cppreference.com/w/cpp/string/byte/memcpy.
Do we want to allow users to pass nullptr to camp::resources::Host::memcpy with a count/size of 0?
In playing with undefined behavior sanitizer I learned that it is undefined behavior to pass a nullptr to std::memcpy even if the count/size argument is 0, see https://en.cppreference.com/w/cpp/string/byte/memcpy.
Do we want to allow users to pass nullptr to camp::resources::Host::memcpy with a count/size of 0?