Thanks for the response. It strikes me that the primitive NRGBA operations
(get pixel, set pixel, and the like) would occur far more common in
practice than encoders, decoders, compress/*, and io, but maybe that's just
how I tend to use images.
On Tuesday, September 28, 2021 at 5:02:48 PM UTC-
On Tue, Sep 28, 2021 at 3:53 AM Scott Pakin wrote:
> I'm curious: Why does image.NRGBA64 define Pix as a []uint8 and
> perpetually pack pairs of uint8 values into a uint16? Wouldn't it have
> been easier and faster to define Pix as a []uint16 and Stride to be a
> stride in uint16s rather than ui
I'm curious: Why does image.NRGBA64 define Pix as a []uint8 and perpetually
pack pairs of uint8 values into a uint16? Wouldn't it have been easier and
faster to define Pix as a []uint16 and Stride to be a stride in uint16s
rather than uint8s?
— Scott
--
You received this message because you
