home.social
Sign in Create account

#gopls — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gopls, aggregated by home.social.

  1. Habr @[email protected] ·

    [Перевод] Go исполнилось 16 лет: главное о развитии языка и экосистемы

    Команда Go for Devs подготовила перевод статьи о том, как Go отмечает шестнадцать лет в Open source. От новых инструментов для тестирования и профилирования до модернизаторов кода, MCP и прорывов в производительности — язык переживает один из самых насыщенных периодов развития.

    habr.com/ru/articles/966700/

    #Go #Go125 #GreenTea #synctest #контейнеры #gopls #MCP #ADK #криптография #производительность

    #производительность #криптография #adk #mcp #gopls #контейнеры
  2. Anders Eknert @[email protected] ·

    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: github.com/go-delve/delve/issu

    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 ( github.com/golang/go/issues/73 ) 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: go-review.googlesource.com/c/t

    #delve #golang #gopls