Thank you for explaining that @brian Hatfield
On Sat, Jul 27, 2019, 00:02 Brian Hatfield wrote:
> Welcome to Go!
>
> There's a couple things going on here, which you can break down into two
> overarching parts.
>
> Part 1, var/type definition:
>
> var testCases = []struct {
> description string
There are several NaNs, but only a single bit pattern for IEEE754 infinity
(modulo the sign bit). So yes, your suggestion should work well. Thank you,
I'll give it a try.
On Sat, Jul 27, 2019, 07:44 Adrian Ho wrote:
> On 26/7/19 9:20 PM, Jan Mercl wrote:
> > In a program that generates C, I'm u
On 26/7/19 9:20 PM, Jan Mercl wrote:
> In a program that generates C, I'm using big.Float.Text
> (https://golang.org/pkg/math/big/#Float.Text) to produce the exact
> value of the C floating point literal. As it turns out, the function
> does not support Inf values. Instead of encoding the exact bit
On Fri, Jul 26, 2019 at 8:15 PM thatipelli santhosh
wrote:
> Can anyone please explain this piece of code? this would be more helpful to
> me to understand this. Thank you!
I don't know what "explain this code" means in this case. But maybe
this can help: https://play.golang.org/p/t4yDlOwG-rv
Welcome to Go!
There's a couple things going on here, which you can break down into two
overarching parts.
Part 1, var/type definition:
var testCases = []struct {
description string
planet Planet
seconds float64
expectedfloat64
}
This says the following things:
- Create a n
Hi ,
I am learning Go step by step. I have go through with slices and structs
but this below code sample is using slices and structs both at a time.
Can anyone please explain this piece of code? this would be more helpful to
me to understand this. Thank you!
var testCases = []struct {
descrip
This is great especially for beginner and hobbist programmers; thank
you very much.
Greetings,
Cleverson
--
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 golang-n
With the recent Gophercon being held I wonder if any videos have been
posted of the talks? I'm especially interested in the move to Go 2 and the
plans for generics.
Thanks.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from th
In a program that generates C, I'm using big.Float.Text
(https://golang.org/pkg/math/big/#Float.Text) to produce the exact
value of the C floating point literal. As it turns out, the function
does not support Inf values. Instead of encoding the exact bits of the
Inf value, the resulting string is s
Well, you can on modern commercial processors for local guards.
It is also very easy to reason why - most lock structures use the same CAS
constructs behind the scenes so you are eliminating operations in all cases.
When you say “faster” you probably mean “fairer” - as most lock free algorithm
On Thu, Jul 25, 2019 at 1:47 PM Robert Engels wrote:
> A sync.Map is lock free on read, and a single lock on writes and so will
> out perform this solution in all cases.
>
>
I wouldn't just matter-of-factly place lock-free algorithms above classical
mutex locks in speed.
--
You received this me
11 matches
Mail list logo
