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

## `map` iteration order is random (no really)

Technically map iteration order is “undefined”. Go maps use a hash
table internally so `map` iteration would normally be done in whatever
order the `map` elements are laid out in that table. This order can’t be relied on and changes as a hash table grow when new elements are added to the map.

In the early days of Go, this was a serious trap for
programmers who didn’t read the instructions and relied on maps
being iterated in a certain order. To help spot these issues early on
rather than in production, Go developers made `map` iterations
random-ish:

# `map` iteration order is random (no really)

Technically map iteration order is “undefined”. Go maps use a hash
table internally so `map` iteration would normally be done in whatever
order the `map` elements are laid out in that table. This order can’t be relied on and changes as a hash table grow when new elements are added to the map.

In the early days of Go, this was a serious trap for
programmers who didn’t read the instructions and relied on maps
being iterated in a certain order. To help spot these issues early on
rather than in production, Go developers made `map` iterations
random-ish:

Basics of Go

Data Types

Collection Types

Control Structures

Functions, Goroutines and Interfaces

Inheritance and Equality

Memory and Time

Wrap Up!

Maps

`map` iteration order is random (no really)