OK, this point of view seems fair enough, I can take that. But won't a normal user would expect that // FooBuffer is some kind of buffer that fails randomly w := FooBuffer(conn) n ,err := m.WriteTo(w) // if binary.Write returns error, n will be 0, buf actual bytes may not be zero.
// n == w.Buffed() ??? it seems just break the interface restriction here... 在 2016年12月16日星期五 UTC+8下午12:51:25，Tamás Gulácsi写道： > > Think from the other side: Write should return the number of bytes > successfully written bytes of the input slice, to allow the caller to retry > from there. > > If your writer writes the bytes in hex, that means it will effectively > write 2n bytes, but must report back n! > > Or a compressor may write less, etc. > > -- 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.
