I don't have a specific situation in mind where I could correct an error returned from Write() but it feels nice to log the error if one occurs just for the sake of knowing. Is that silly? I'm picturing that it could be helpful if there is a spike in network trouble because then you would be able to detect it and maybe contact someone about it. Or maybe that is silly too? The problem I have is that I don't understand well enough what Write() does under the hood AND I don't believe I've even seen Write() fail so I have no experience on the subject.
On Sunday, October 22, 2017 at 10:38:10 AM UTC-5, Jakob Borg wrote: > > On 22 Oct 2017, at 17:29, "groene...@gmail.com <javascript:>" < > groene...@gmail.com <javascript:>> wrote: > > So do you think this error should be checked and if yes, under what > circumstances? > > > I think Tamás already answered this. If you need to know whether the write > succeeded and can do something reasonable about it if it didn’t, check it I > guess. I don’t think I’ve seen a situation yet where that applies. Also > keep in mind that just because the write succeeded the bytes may not > necessarily ever reach the client. > > //jb > -- 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. For more options, visit https://groups.google.com/d/optout.
