Subject: copy_and_convert_pixels and overlapping views
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2018-10-01 17:07:10
Do we know what are limitations/guarantees regarding
input image underlying the source and destination views
when applying the copy_and_convert_pixels algorithm?
Can both, source and destination, be based on the same image,
pixel data buffer? Are overlapping ranges accceptable by design?
For example, is this kosher GIL code?
PixelType* pixels = ...;
auto src = interleaved_view(width, height, pixels, rowsize_in_bytes);
auto dst = interleaved_view(width, height, pixels, rowsize_in_bytes);
Can we document such requirements/constraints?
-- Mateusz Loskot, http://mateusz.loskot.net
Boost list run by Boost-Gil-Owners