Also, it would be simpler to not run the copy in a go routine until you verify that is working as expected. Then use wait groups to control the go routine lifecycle. On Sep 19, 2024, at 8:51 AM, Robert Engels <reng...@ix.netcom.com> wrote: -- 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/59D3B652-30F5-43B7-AA52-76D1113C9BFE%40ix.netcom.com. |
- [go-nuts] io.Copy(conn, os.Stdin) do not work as expected 李世民
- Re: [go-nuts] io.Copy(conn, os.Stdin) do not work as ex... Robert Engels
- Re: [go-nuts] io.Copy(conn, os.Stdin) do not work a... Robert Engels