[go-nuts] Calling sync.WaitGroup.Add() while a sync.WaitGroup.Wait() is waiting

Hello, We were having a discussion at work about passing around references to sync.WaitGroup. I said it was a bad idea, because if a goroutine launched a goroutine of its own and called sync.WaitGroup.Add() after a goroutine called sync.WaitGroup.Wait(), but before the count dropped to 0, your

Re: [go-nuts] Calling sync.WaitGroup.Add() while a sync.WaitGroup.Wait() is waiting

Thanks, everyone, for your answers! I think I understand what sync.WaitGroup is doing now. Jon On Friday, April 27, 2018 at 7:29:50 AM UTC-4, rog wrote: > > On 26 April 2018 at 16:29, Jon Bodner > > wrote: > > Hello, > > > > We were having a discussio

[go-nuts] Quick question about the new Contracts Draft Proposal

Hello, I did a first read through the proposal and it looks very good. I had one question: when giving the example of how to implement Sorting using orderedSlice, the type parameter is declared to be comparable. Should that be contracts.Ordered? Thanks, Jon -- You received this message be

[go-nuts] Re: Quick question about the new Contracts Draft Proposal

https://go.googlesource.com/proposal/+/master/design/go2draft-contracts.md (Updated on 7/25/2019) GopherCon 2019 Talk summary: https://about.sourcegraph.com/go/gophercon-2019-generics-in-go Jon On Sunday, July 28, 2019 at 7:55:50 PM UTC-4, Mandolyte wrote: > > I missed this. Do you have a link

[go-nuts] Re: Do you guys use ORMs when working with SQL?

I've written a library called Proteus that is a simple tool for dynamically generating a data access layer: https://github.com/jonbodner/proteus You need to write the SQL queries, but it will map values (variables, slices, structs, maps) into queries and map the results into a struct or map.

[go-nuts] Unsure when two interfaces are considered identical

Hello, I'm working on a DAO adapter layer helper called Proteus (https://github.com/jonbodner/proteus), and ran into an interesting quirk in what Go considers equivalent interfaces. I recreated a simplified version of the issue is at https://play.golang.org/p/BS3-bUKtO9 . The code that I linke

Re: [go-nuts] Unsure when two interfaces are considered identical

Jon On Sunday, July 3, 2016 at 11:29:32 PM UTC-4, Ian Lance Taylor wrote: > > On Sun, Jul 3, 2016 at 12:27 PM, Jon Bodner > wrote: > > > > I'm working on a DAO adapter layer helper called Proteus > > (https://github.com/jonbodner/proteus), and ran into an

Re: [go-nuts] Unsure when two interfaces are considered identical

ause > the compiler considers unclear what should be achieved. > > > > > > > On Monday, July 4, 2016 at 5:29:32 AM UTC+2, Ian Lance Taylor wrote: >> >> On Sun, Jul 3, 2016 at 12:27 PM, Jon Bodner >> wrote: >> > >> > I'm working

Re: [go-nuts] Unsure when two interfaces are considered identical

esult, it should > always mention it. > > Regards, > > On Monday, July 4, 2016 at 5:16:57 PM UTC+2, Jon Bodner wrote: >> >> Hi Constantin, >> >> Thanks for responding. >> >> This is a case where I think the compiler should be perfectly capable of >> f

[go-nuts] reflect.StructOf oddity

Hi all, I was writing up an example to demonstrate that embedded fields in a dynamically generated struct don't delegate. Except that I somehow made one that did: https://play.golang.org/p/TWApy-JibG What's extra-odd is that the behavior is completely wrong; it's doubling off of the wrong fie

Re: [go-nuts] reflect.StructOf oddity

aylor wrote: > > On Tue, Jun 27, 2017 at 11:06 AM, Jon Bodner > wrote: > > > > I was writing up an example to demonstrate that embedded fields in a > > dynamically generated struct don't delegate. Except that I somehow made > one > > that did:

Re: [go-nuts] reflect.StructOf oddity

https://github.com/golang/go/issues/20824 On Tuesday, June 27, 2017 at 10:34:19 PM UTC-4, Jon Bodner wrote: > > Hi Ian, > > I'll file the bug report. Thanks for explaining how wrapper methods work. > I have a second test case with a pointer (and a successful attempt to >