Early this year I filed an issue in the #delve debugger repo about how some type names were displayed not by their name but their fully "resolved" path: https://github.com/go-delve/delve/issues/3910
As trivial as that may seem, it makes debugging almost useless for the deeply recursive #golang code I normally work on when all you see is incredibly long strings cluttering up the view.
I had almost forgotten about this until another issue I filed in Go's #gopls tool ( https://github.com/golang/go/issues/73661 ) got fixed, but the fix came with another issue... I'm sure you can guess which one.
I had previously assumed that type names getting "expanded" to paths was an oversight where it occured, but it seems like pretty printing type names in Go is a non-trivial problem: https://go-review.googlesource.com/c/tools/+/671915/1..3/gopls/internal/analysis/modernize/slices.go#b192