Gain insights into Go's unique features, delve into advanced memory handling, strings, loops, and goroutines. Discover how to handle multidimensional datasets and protect against variable bugs.

go.tar.gz

unicode_norm

equality_test

equality_bench

memory_first

imports_pkg

exercise

SPA test

Run packages

Go is a popular language known for its simplicity. For developers who lack a deep knowledge of its features, it's a great time to pick up the Go language. The differences between Go and other popular programming languages can lead to hours of Google for the newer software engineer. Mastering these surprising, sometimes delightful, sometimes frustrating features can be the difference between time spent on debugging and time spent on deployment.

In this course, you will go deeper than an introductory book to learn the various features that make Go unique. You’ll learn how to protect against the bugs caused by poorly defined variables (and variable shadowing), how Go treats slicers and arrays similarly, and how to work with multidimensional datasets. You’ll also dive into memory handling, strings, loops, and goroutines.

This course will be most useful if you already have a basic understanding of Go and its syntax. By the end of the course, you’ll move from Go-familiar to Go-expert.

Exploring and Mastering the Full Go Featureset

## Should structs be passed by value or by reference

Arguments to Go functions are always passed by value. When a
`struct` (or array) type variable is passed into a function, the whole
`struct` gets copied. If a pointer to a `struct` gets passed, then the
pointer is copied, but the `struct` it points to isn't. 8 bytes of memory
(for 64bit architectures) get copied instead of whatever the size of
the `struct` is. So does that mean it’s better to pass structs as
pointers? As always - it depends.

Taking a pointer to a struct (or array):
1) places it in heap memory
rather than stack where it would normally be
2) involves a garbage
collector to manage that heap allocation.

Stack is fast and heap is slow. That means if you allocate structs more than pass them around, it's
way faster to let them be copied on stack:

# Should structs be passed by value or by reference

Arguments to Go functions are always passed by value. When a
`struct` (or array) type variable is passed into a function, the whole
`struct` gets copied. If a pointer to a `struct` gets passed, then the
pointer is copied, but the `struct` it points to isn't. 8 bytes of memory
(for 64bit architectures) get copied instead of whatever the size of
the `struct` is. So does that mean it’s better to pass structs as
pointers? As always - it depends.

Taking a pointer to a struct (or array):
1) places it in heap memory
rather than stack where it would normally be
2) involves a garbage
collector to manage that heap allocation.

Stack is fast and heap is slow. That means if you allocate structs more than pass them around, it's
way faster to let them be copied on stack:

Basics of Go

Data Types

Collection Types

Control Structures

Functions, Goroutines and Interfaces

Inheritance and Equality

Memory and Time

Wrap Up!

Memory Management

Should structs be passed by value or by reference