> However, are Go programs not supposed to typically avoid sharing mutable data across goroutines in the first place?

C programmers aren’t supposed to access pointers after freeing them, either.

“Easy to do, even in clean-looking code, but you shouldn’t do it” more or less is the definition of a pitfall.