This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Go · Archive · Week 25 · Jun 16 – 22, 2025

hash/maphash: standardize the hash function

Worth knowingstdlib

What changed
The proposal adds a generic Hasher[T any] interface and a ComparableHasher[T comparable] implementation to package maphash.
Production impact
The source does not say.
Try it
Import maphash and declare a type that implements Hasher[int] to see the new API.
Source
github.com/golang/go/issues/70471

Understand it, then run it

The Go standard library has a package called hash/maphash that is used internally by maps to compute hash values. In older versions, the package did not expose a clear way for users to define their own hash functions for custom types. The change adds a generic interface called Hasher[T any] and a helper type ComparableHasher[T comparable]. Hasher describes two methods: Hash, which writes the hash of a value into a maphash.Hash, and Equal, which tells whether two values are considered the same for hashing purposes. ComparableHasher implements this interface for any type that already supports the == operator, so you can use it without writing extra code. With this change you can now write your own hash logic that works with Go’s map implementation, rather than relying on the default hashing of built‑in types.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed