On Wed, May 22, 2019 at 9:02 AM Robert Engels <reng...@ix.netcom.com> wrote: > > The more I think about this, the more I believe that this is a horrible > situation that breaks all rules of encapsulation. This requires the creator > to maintain references to the underlying Writer. It also requires the creator > to be the sole decider of when the Writer is closed, or the creator must pass > the concrete class to subordinates so they can close, or the subordinates > must do type casting. > > The bufio.Writer is badly broken and should be changed to declare Close and > pass this to the contained Writer if it is a WriterCloser.
What to open a proposal for that? https://golang.org/s/proposal. Ian -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXC65fYWGYS4034Gdor0_MHT9E%3DM7kp7S9nfvepR-js2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
