Setup Go Environment

go.md

Install & Setup

• Download Go: https://golang.org/dl/
• Create a go folder in local machine, in this case ~/go

Note: all the go code should be inside this go folder

• Set your GOPATH

export GOPATH=$HOME/go
export PATH=$PATH:$GOPATH/bin
echo "export GOPATH=$HOME/go" >> .bash_profile

• Check if install & setup successfully

1. Create hello.go in ~/go/src/hello/ with the following code

package main
import "fmt"
func main() {
  fmt.Println("ok")
}

2. Then go run hello.go

ok

You can only declare a method with a receiver whose type is defined in the same package as the method. You cannot declare a method with a receiver whose type is defined in another package (which includes the built-in types such as int).

Pointer Receivers are more common than value receivers

Methods with pointer receivers can modify the value to which the receiver points (as Scale does here). Since methods often need to modify their receiver, pointer receivers are more common than value receivers.

With a value receiver, the Scale method operates on a copy of the original Vertex value. (This is the same behavior as for any other function argument.) The Scale method must have a pointer receiver to change the Vertex value declared in the main function.

type Vertex struct {
	X, Y float64
}
func (v *Vertex) Scale(f float64) {
	v.X = v.X * f
	v.Y = v.Y * f
}
func (v Vertex) Scale1(f float64) {
	v.X = v.X * f
	v.Y = v.Y * f
}
func main() {
	v := Vertex{3, 4}
	v.Scale1(10)
	fmt.Println(v)
	v.Scale(10)
	fmt.Println(v)
}

Output

{3 4}
{30 40}

Choosing a value or pointer receiver

There are two reasons to use a pointer receiver.
The first is so that the method can modify the value that its receiver points to.
The second is to avoid copying the value on each method call. This can be more efficient if the receiver is a large struct, for example.
In general, all methods on a given type should have either value or pointer receivers, but not a mixture of both.

Waitgroup

A WaitGroup waits for a collection of goroutines to finish. The main goroutine calls Add to set the number of goroutines to wait for. Then each of the goroutines runs and calls Done when finished. At the same time, Wait can be used to block until all goroutines have finished.

func main() {
	wg := sync.WaitGroup{}

	data := make(chan int)
	wg.Add(2)
	go func() {
		for i := 0; i < 100; i++ {
			fmt.Println("Received ", <-data)
		}
		wg.Done()
	}()

	go func() {
		for i := 0; i < 100; i++ {
			data <- i
		}
		wg.Done()
	}()
	wg.Wait()
}

Buffered Channel

func main() {
	wg := sync.WaitGroup{}
	data := make(chan int, 100)
	wg.Add(2)
	go func() {
		for num := range data {
			fmt.Println("Received ", num)
		}
		wg.Done()
	}()

	go func() {
		for i := 0; i < 100; i++ {
			data <- i
		}
		close(data)
		wg.Done()
	}()
	wg.Wait()
}

Mutex

A Mutex is a mutual exclusion lock. The zero value for a Mutex is an unlocked mutex.

Working with JSON

Marshal vs UnMarshal

type person struct {
	First string `json: "First"`
	Last  string `json: "Last"`
	Age   int    `json: "Age"`
}

func main() {
	// struct to json
	p1 := person{"james", "bond", 32}
	p2 := person{"money", "pendy", 38}
	people := []person{p1, p2}
	fmt.Println(people)
	bs, err := json.Marshal(people)
	if err != nil {
		fmt.Println(err)
	}
	jsonString := string(bs)
	fmt.Println(jsonString)

	// json to struct
	bs1 := []byte(jsonString)
	var people1 []person
	err1 := json.Unmarshal(bs1, &people1)
	if err1 != nil {
		fmt.Println(err1)
	}
	fmt.Println(people1)
}

Concurrency is Not Parallelism, it is a design pattern that makes your code to run better on Multiple Core Computer