Yes, I already addressed this but I know people often reply as they read. This is not really a pipe in the traditional posix sense. A bad name, or bad implementation imo.
> On Nov 21, 2019, at 10:53 PM, Jamil Djadala <djad...@datamax.bg> wrote: > > On Thu, 21 Nov 2019 22:37:37 -0600 > Robert Engels <reng...@ix.netcom.com> wrote: > >> The OP specifically requested io.Reader/Writer interfaces. >> >> A pipe is what he wants. Not a ring buffer. (A pipe essentially has a >> ring buffer in the implementation though). > > from https://golang.org/pkg/io/#Pipe : > > The data is copied directly from the Write to the corresponding Read > (or Reads); there is no internal buffering > > and looking in implementation, it seems that internally Pipe is using > channel. > > -- > Jamil Djadala > > -- > 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/20191122065315.78316d02%40wolf.home. -- 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/AC4A7316-7473-406B-8B4A-17609E836E20%40ix.netcom.com.
