[go-nuts] Guidance in naming.

2017-09-21 Thread M2
We have the same library in multiple languages. All the other languages name a specific class/struct fooContext. In Go that data structure stores some metadata to be propagated by the "context".Context? Is it ok to name it "fooContext" in Go also to stay consistent with the other languages even

[go-nuts] Re: Guidance on exposing functionality

2017-06-06 Thread M2
TC-7, Matt Layher wrote: > > Approach number one is the correct way, IMO. > > That's what I've always done: > https://godoc.org/github.com/mdlayher/netlink#Conn.Execute. > > - Matt > > On Tuesday, June 6, 2017 at 3:56:43 PM UTC-4, M2 wrote: >> >> I

[go-nuts] Guidance on exposing functionality

2017-06-06 Thread M2
I need to expose 2 ways of doing the same thing. - The first way is very simple, always does the right thing and is impossible to use improperly. It is expected to be used by the majority of users. - The second one can be used improperly but offers more flexibility. It is expected to be used by