Panel With The Go Team
summary
Discussion hits practical limits: cgo with MSVC not supported today and needs Windows experts or external patches; people use Zig CC as a portable C cross-compiler workaround. Big change was generics in Go 1.18, still being polished; fuzzing and a curated vulnerabilities DB are active efforts. Struct-field auto-reordering is avoided for surprising compatibility, and x/text and plugin maintenance rely on external contributors. File bugs or proposals in the golang/go GitHub repo and check x/exp for experimental containers and slices.
AI-written summary · about
chapters (16)
- 0:00Introductions and roles
- 1:32Cgo and msvc integration
- 4:50Go's usability and goal
- 6:16Compiler optimizations
- 9:18The future of Go
- 10:44Improving cgo performance
- 14:38Structure field alignment
- 17:34Cross-compiling with cgo
- 21:24Go's innovation strategy
- 26:30Development governance
- 30:17Maintaining packages
- 32:37Error handling in Go
- 35:35Intrinsic support
- 40:20Container types
- 43:08Testing improvements
- 48:53Object-oriented programming
