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
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
Ok, thank you.
Vladimir, is there any resource to read about current and probably future
of the go profiling ?
In fact it is not only very important but and very, very interesting.
Thank you.
вторник, 28 сентября 2021 г. в 06:38:31 UTC+3, vlad...@varank.in:
> Hello,
>
> I suspect this is due
Hi All,
Last year, I had asked something similar about comparing QuickUnion with
QuickFind although that turned out to be a flaw in my benchmarking function.
This time, I am comparing the QuickUnion with WeightedQuickUnion.
I ran benchmarking on this code and noticed that the WeightedQuickUnion
