Re: [go-nuts] interface{private()}

On Thu, Jun 20, 2019 at 5:49 PM Gert wrote: > > Thanks, does the go standard library have a use case where a private() > function in a interface is needed? Looking for more examples to understand > the benefit to do so. Yes, in the go/ast package (and possibly elsewhere, but that's the example

Re: [go-nuts] interface{private()}

Thanks, does the go standard library have a use case where a private() function in a interface is needed? Looking for more examples to understand the benefit to do so. On Friday, June 21, 2019 at 2:36:01 AM UTC+2, Ian Lance Taylor wrote: > > On Thu, Jun 20, 2019 at 5:25 PM Gert > > wrote: > >

Re: [go-nuts] interface{private()}

On Thu, Jun 20, 2019 at 5:25 PM Gert wrote: > > Trying to get my mind around why the private() function is necessary here. I > fail to understand the comment provided > > type Geometry interface { > GeoJSONType() string > Dimensions() int // e.g. 0d, 1d, 2d > Bound() Bound > > // requirin

[go-nuts] interface{private()}

Trying to get my mind around why the private() function is necessary here. I fail to understand the comment provided type Geometry interface { GeoJSONType() string Dimensions() int // e.g. 0d, 1d, 2d Bound() Bound // requiring because sub package type switch over all possible types. pr