On Monday, July 7, 2025 at 8:48:03 AM UTC-7 Robert Engels wrote:
This change seems wrong just based on the io.Reader returns of valid bytes and an error. I'm not sure what you are saying. This change (CL 657715) is just about doing (pointer) nil checks where the spec says they should go. There are no nil checks when using the first result of an io.Reader.Read call. If you think there is a problem, please find a program demonstrating the problem. An error doesn’t always mean the other return values are invalid - it is decided by the api method. 100% agree. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/078de003-d657-4655-992a-5e8ec09e715dn%40googlegroups.com.
