Why is Go Map Iteration Unordered, and How Can I Guarantee Order?

Go Map Printing Out of Order

In Go, maps are implemented using a hash table, which maintains key-value pairs in a non-ordered fashion. As a result, iterating over a map does not guarantee the order in which keys or values will be returned.

Why is the Map Printing Out of Order?

In the provided code, the map months is defined with key-value pairs representing the month numbers and corresponding names. When iterating over the map using a range, the order of the printed output is based on the internal implementation of the hash table, which is typically optimized for performance rather than order.

How to Fix the Order

There are several approaches to ensure the order of map iteration:

1. Use an Ordered Map:

Go does not have a built-in ordered map type, but there are third-party libraries that provide this functionality. One such library is "github.com/golang/collections#OrderedMap."

import "github.com/golang/collections#OrderedMap"

func main() {
    m := collections.NewOrderedMap()
    m.Set(1, "January") // ...

    for _, month := range m.Keys() {
        fmt.Println(month, "-", m.Get(month))
    }
}

2. Sort the Map Keys:

Another option is to get the keys from the map, sort them, and then iterate over the sorted keys to access the values in order.

func main() {
    keys := make([]int, 0, len(months))
    for k := range months {
        keys = append(keys, k)
    }

    sort.Ints(keys)

    for _, k := range keys {
        fmt.Println(k, "-", months[k])
    }
}

The above is the detailed content of Why is Go Map Iteration Unordered, and How Can I Guarantee Order?. For more information, please follow other related articles on the PHP Chinese website!