jbamsterdam

No, it does not. The length of the pattern isn't important anymore, only whether it overlaps with other patterns.

I find I rarely need equality checks beyond simple types like ints, strings and times. The big exception to that is tests, for which I recommend cmp (https://pkg.go.dev/github.com/google/go-cmp/cmp).

Nothing's changed, and that's still an issue. We didn't address it because the post was long enough, but as Merovius himself says, it's called out in the Go 1 compatibility promise. So the Go standard library doesn't worry about it, and neither should you. It's also extremely rare; I've never seen it in 10 years of Go programming.

Until gorelease is ready, you can try apidiff (https://go.googlesource.com/exp/+/refs/heads/master/cmd/apid...).

Do you have any specific examples in mind?

Despite the title, the problems that this article discusses could have happened even before modules were introduced. Before modules, your only choices were to stay compatible or break users. Modules give us the freedom to make breaking changes in a safe, documented way.