Anders Eknert<p>Early this year I filed an issue in the <a href="https://swecyb.com/tags/delve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>delve</span></a> debugger repo about how some type names were displayed not by their name but their fully "resolved" path: <a href="https://github.com/go-delve/delve/issues/3910" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/go-delve/delve/issu</span><span class="invisible">es/3910</span></a></p><p>As trivial as that may seem, it makes debugging almost useless for the deeply recursive <a href="https://swecyb.com/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> code I normally work on when all you see is incredibly long strings cluttering up the view. </p><p>I had almost forgotten about this until another issue I filed in Go's <a href="https://swecyb.com/tags/gopls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gopls</span></a> tool ( <a href="https://github.com/golang/go/issues/73661" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/golang/go/issues/73</span><span class="invisible">661</span></a> ) got fixed, but the fix came with another issue... I'm sure you can guess which one. </p><p>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: <a href="https://go-review.googlesource.com/c/tools/+/671915/1..3/gopls/internal/analysis/modernize/slices.go#b192" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">go-review.googlesource.com/c/t</span><span class="invisible">ools/+/671915/1..3/gopls/internal/analysis/modernize/slices.go#b192</span></a></p>