Re: [go-nuts] [generics] combining different instances of the same generic type

2020-12-01 Thread Matt Joiner
Thanks very much for taking a look at this Roger. I think your attempt differs from mine in that you don't make use of the future type F in implementing the waiting for the blocks of delayed futures, which means you don't have to deal with combining different instances of F (F[A], F[B] etc.). Also

Re: [go-nuts] [generics] combining different instances of the same generic type

2020-12-01 Thread roger peppe
And again (no need to make a cancelable context) https://go2goplay.golang.org/p/3UFUaXijuX9 On Tue, 1 Dec 2020 at 22:59, roger peppe wrote: > Slightly simpler again: https://go2goplay.golang.org/p/mKdishv4nhT > > On Tue, 1 Dec 2020 at 18:44, roger peppe wrote: > >> I'm having difficulty underst

Re: [go-nuts] [generics] combining different instances of the same generic type

2020-12-01 Thread roger peppe
Slightly simpler again: https://go2goplay.golang.org/p/mKdishv4nhT On Tue, 1 Dec 2020 at 18:44, roger peppe wrote: > I'm having difficulty understanding exactly what your code is trying to do > (and why), and that makes it hard to understand what > generic solution might be appropriate. > > Howe

Re: [go-nuts] Question about blog post: https://blog.golang.org/pipelines

2020-12-01 Thread nc
Great, thanks for that clarification. On Tuesday, December 1, 2020 at 4:51:11 PM UTC-4 Jan Mercl wrote: > On Tue, Dec 1, 2020 at 9:05 PM nc wrote: > > I just wanted to know if there was a way to tell that the goroutines c1, > c2 actually are hung. Could I in my head add the sentences "While the

Re: [go-nuts] Question about blog post: https://blog.golang.org/pipelines

2020-12-01 Thread Jan Mercl
On Tue, Dec 1, 2020 at 9:05 PM nc wrote: > I just wanted to know if there was a way to tell that the goroutines c1, c2 > actually are hung. Could I in my head add the sentences "While the program > terminates, that is only because the main goroutine has finished its > execution. One of the send

[go-nuts] Question about blog post: https://blog.golang.org/pipelines

2020-12-01 Thread nc
Hello, This is my first time on this mailing list. I'm trying to learn about Go concurrency patterns. I am looking at the Stopping Short section and in particular at the following code: https://blog.golang.org/pipelines#TOC_5.:~:text=%2F%2F%20Consume%20the%20first%20value%20from%20the,%7D I t

Re: [go-nuts] Minisign for x/crypto

2020-12-01 Thread 'Péter Szilágyi' via golang-nuts
Hello, Though so ourselves too but figured an email won't hurt :) Cheers, Peter On Tuesday, December 1, 2020 at 8:48:23 PM UTC+2 Filippo Valsorda wrote: > Hi Peter, > > There is already github.com/jedisct1/go-minisign from the minisgn author, > so I don't think this needs to live in x/cryp

Re: [go-nuts] Minisign for x/crypto

2020-12-01 Thread Filippo Valsorda
Hi Peter, There is already github.com/jedisct1/go-minisign from the minisgn author, so I don't think this needs to live in x/crypto. Cheers, Filippo On Wed, Nov 18, 2020 at 3:01 AM Ian Lance Taylor wrote: > [ + Filippo ] > > On Tue, Nov 17, 2020 at 12:56 PM 'Péter Szilágyi' via golang-nuts >

Re: [go-nuts] [generics] combining different instances of the same generic type

2020-12-01 Thread roger peppe
I'm having difficulty understanding exactly what your code is trying to do (and why), and that makes it hard to understand what generic solution might be appropriate. However, here's one alternative implementation that doesn't seem to run into the same kind of issues that you did. It changes the c