Skip to main content

One Step, Any Size

O(1) means constant time: the operation takes the same number of steps whether the input has 5 elements or a million. The work does not grow at all.

This is the best complexity there is. Typical O(1) operations in Go are: reading a slice element by index, reading a map value by key, len(), appending one element, and simple math.

Note what O(1) does not mean: it does not mean "fast", it means "does not get slower when the input grows". One constant step can still be a slow step — but it stays one step.


Slice and Map Lookups

A slice element lives at a known position in memory, so words[2] is one jump — the computer does not walk through the elements before it. The same read costs the same in a slice of one million elements.

A map lookup like ages["Ben"] also takes constant time on average: the key tells the map directly where the value is stored. The lookup returns value, ok, and ok is false when the key is missing.

Read an element by index

The program reads one element from a 5-element slice and one from a slice with a million elements. Both reads are a single step — the slice length plays no role.

Prompt
Write a Go program with a small slice of 5 words and a big slice of one million ints built with make and a loop. Read one element from each by index and print both, to show that reading by index is one step no matter how long the slice is.
Output: Go program and captured output
Read an element by index

Read a value by key

ages["Ben"] finds 25 directly. The missing key "Dan" returns the zero value 0 and ok == false — still in constant time.

Prompt
Write a Go program with a map from names to ages holding Ana 30, Ben 25 and Cleo 41. Look up Ben and print the value and the ok flag. Then look up the missing key Dan and print the value and the ok flag.
Output: Go program and captured output
Read a value by key

Appending and Simple Math

append() adds one element at the end of a slice. Most of the time that is one step. (Once in a while the slice must grow and gets copied, but averaged out the cost per append stays constant.)

All the small operations — assignments, additions, comparisons, swapping two values — are O(1) too. They are the "steps" that all the other complexity classes are counted in.

Append one element

append() puts "yellow" at the end. The cost does not depend on how many colors are already in the slice.

Prompt
Write a Go program with a slice holding red, green, blue. Print the slice and its length, append yellow, then print the slice and its length again.
Output: Go program and captured output
Append one element

Swap two values

a, b = b, a swaps the two values in one constant-time step — no helper variable needed.

Prompt
Write a Go program with two variables a = 1 and b = 2. Print them, swap them with the two-value assignment a, b = b, a, and print them again.
Output: Go program and captured output
Swap two values