/docs/Recent content in Labs on Go Basics TrainingHugo -- gohugo.ioen/docs/project-structure/Mon, 01 Jan 0001 00:00:00 +0000/docs/project-structure/Basics A Go project usually consists of exactly one module. Every directory within the project is a package. Hence a module is a collection of packages. So usually we can say: Module = Project = Git Repository Package = Directory Module path To create a new Go project in the current directory we initialize a new module by running go mod init <module-path>. If we want to create a new project named myproject we would do the following steps:/docs/testing/Mon, 01 Jan 0001 00:00:00 +0000/docs/testing/Writing Tests Tests are defined as functions in the following form: func TestXxx(t *testing.T) The tests reside in the same directory as the source code. The test files end with _test.go. The code in these files is not compiled into the binary when building the project. For demonstration purposes we put the function and test in the same code block. These are usually in a different file (e.g. calculator.go and calculator_test./docs/concurrency/Mon, 01 Jan 0001 00:00:00 +0000/docs/concurrency/Goroutines To run multiple functions concurrently we can start Goroutines. You can think of a Goroutine as a lightweight thread managed by the Go runtime. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 package main import ( "fmt" "time" ) func print(word string) { for i := 0; i < 5; i++ { fmt.Println(word) time.Sleep(100 * time.Millisecond) } } func main() { go print("hello") print("world") } Output: world hello world hello hello world world hello hello world When the main function returns, the program exits./docs/generics/Mon, 01 Jan 0001 00:00:00 +0000/docs/generics/The Go 1.18 release (February 2022) adds support for generics. In the following section, we will take a look at the new language feature but we will not cover every detail. Why do we need Generics Imagine you implement a function contains to check wheter a certain item is in a list: func contains(list []int, item int) bool { for _, current := range list { if current == item { return true } } return false } The function above only works for slices of the type int./docs/packaging/Mon, 01 Jan 0001 00:00:00 +0000/docs/packaging/Basics Go binaries are statically linked. That means all dependencies are included within the binary. go build main.go The binary will only work on the same platform that built it (e.g. 64bit Linux). Go allows us to easily generate binaries compatible with other architectures: GOOS=linux GOARCH=arm64 go build main.go GOOS=windows GOARCH=amd64 go build main.go Docker The Dockerfile uses multi-stage builds so that the resulting image is small and secure. The image is built with the full Golang Docker image and the resulting binary is copied into the Distroless image .