However quite a few Go developers now use interfaces with an unexported method specifically to stop users from misusing their types in a context they didn't intend. I guess it's come full circle.
What a horrible hack. Why bother with that? Either export your interface, your don't.
Indeed. It's used in the standard library for describing Go's AST if I recall correctly.
The whole point is that the caller can make new interfaces to fit existing structs in other libraries.
All this pain for what boils down to not having to make a wrapper. Sure wrappers are dumb, but pushing a static analysis out to a run time error dumber, especially since implementing interfaces is a lot more common than wrapping 3rd party structs.
The latter is wonderful, and other languages support this without needing to resort to the former.