mactsouk / mastering-go-3rd Goto Github PK

//fixing syntax error on numeric.go (ch13) line 8:
package main

import (
"fmt"
)

type Numeric interface {
int | int8 | int16 | int32 | int64 | float64
}

func Add[T Numeric](a, b T) T {
return a + b
}

func main() {
fmt.Println("4 + 3 =", Add(4,3))
fmt.Println("4.1 + 3.2 =", Add(4.1,3.2))
}

From:

Why is os.Exit() called for SIGINFO. I tried this locally with SIGUSR1 and executing:

$ kill -USR1 <pid>

caused the complete process to exit not just the go routine. The <pid> didn't exist anymore and the process had terminated.
When I tried the same example by commenting out os.Exit(), it worked perfectly fine and the for loop was still continuing and the go routine hadn't exited.

I am on Ch-06 right now so my knowledge about goroutines and channels is limited.

Why isn't the code for chap 12 available?

When implementing the GetRandom method you are suddenly using a function method(min, max).
Where is this function coming from? What are min and max?

https://github.com/mactsouk/mastering-Go-3rd/blob/f405912e1d54150eb6414afcf7fbbf0a71cd7cb2/ch13/allowed.go#:~:text=f405912e1d-,mastering%2DGo%2D3rd,Go%20to%20file,-mactsouk%20Initial%20Public

func Same[T comparable](a, b T) bool {
if a == b {
return true
}
return false
}

as

func Same[T comparable](a, b T) bool {
return a == b
}

@mactsouk may be not a big deal here as you are explaining about generics?

with the line 47 of the code sliceArrays.go,it says:

// This change does not go to S12
a[1] = "-N2-"

but Actually, the changes of a[1] does go to S12 !

By the way , the Book is right: "However, array a and slice S12 are still connected because the capacity of S12 has not
changed."

In the book it's written about this code:

The preceding naively implemented example creates 4 go-routines

However there 5 go-routines created in the actual code (other than main) indexed: 0, 1, 2, 3, 4

When the first argument is non-parseable, the min/max variables are not initialized to the first parseable argument (but to 0 by default). This would lead to bug when all the parseable arguments share the same sign.