I believe that the result is the least significant bit, not byte.
John
John Souvestre - New Orleans LA
From: [email protected] [mailto:[email protected]] On
Behalf Of Pablo Rozas Larraondo
Sent: 2017 July 23, Sun 07:51
To: golang-nuts
Subject: [go-nuts] Understanding least significant byte operation
I have seen Go code using this function to find out the least significant byte
of unsigned integers:
func LSB(ci uint64) uint64 { return uint64(ci) & -uint64(ci) }
This function works fine but I wonder why, if call the same AND operation, it
results in an error: "constant -X overflows uint64"
Here is a playground example to illustrate this:
https://play.golang.org/p/_0EYtlLnmG
Does anyone know what changes when -uint64() is called in a return statement?
How a negative uint should be interpreted?
Thank you,
Pablo
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
