ied something similar?
Should I expect obvious problems for downstream consumers, like
failed builds?
Is there an alternative solution to be considered?
Thanks,
Rodolfo Carvalho
PS: the module graph pruning <https://github.com/golang/go/issues/36460>
from Go 1.17 <https://go.dev/d
This is a question about organizing table tests.
I believe the most common idiom for writing table tests is to store test
cases in a slice of structs like in the example from
https://github.com/golang/go/wiki/TableDrivenTests
(p), nil
}
What's the advantage of using an int in this case, if any?
Thank you,
Rodolfo Carvalho
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to g
Thanks everyone for the answers and links.
I computed a pixel-to-pixel difference and indeed what I was getting was
-1/+1 differences in the gray values, due to rounding.
Next free time I'll try the other formulas.
Thank you again,
Rodolfo Carvalho
On Thu, Sep 29, 2016 at 6:12 AM, Micky
#expand_body_buiz8mj-9
[6] Octave:
https://sourceforge.net/p/octave/image/ci/default/tree/inst/rgb2gray.m#l43
Thanks,
Rodolfo Carvalho
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving e