Go Tooling
summary
Panel describes concrete tooling work: the language server gopls powers completions and refs, a new debug adapter (Delve backend, DAP) is at v0 and lands in VS Code nightly, and the plan adds logpoints and conditional breakpoints. Fuzzing ships as test-like targets via f.Fuzz and f.Add to seed corpora so existing table tests convert easily. package.go.dev shows imported by, docs and test counts as signals. Module mirror and checksum DB provide reliable, auditable fetches; a workspace module/work file is proposed for multi-module editing.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:54What Is the Go Tools Team Who's on It and What Do You Do Who Wants
- 3:06The Go Tools Team
- 6:46Go Security Team
- 20:15Stability
- 32:54Conditional Break Point
- 42:49What Should We Be Looking Out for in the Next Releases
- 43:29Multi-Module Workspaces
- 44:03The Workspace Module
- 45:33Support for Multi-Module Workspaces
- 45:56Vs Code Plugin
- 48:27How Can We Contribute to the Go Community
- 49:07What's the Module Mirror and Checksum Database and What Does that Provide for Go Developers
- 53:11The Vulnerability Database
