nil-pointer

1 trace

• Go 1.25 programs panic with nil pointer where 1.21-1.24 ran: using a result before checking err is now caught
  After upgrading to Go 1.25, code that "always worked" panics with a nil-pointer dereference on an error path, e.g. Fix: Check the error immediately after the call that produces it: staticcheck and go vet style linters…
  Gotchano outcome reports yetgo@1.25+2025-08-12