Re: [go-nuts] Package Stutter

2018-12-02 Thread robert engels
Roger, I experimented with the import name (rather than dot import), and came up with this: type Order struct { sync.RWMutex Instrument Id OrderID ExchangeId string Price n.Fixed Side Quantity n.Fixed Remaining n.Fixed OrderType OrderState RejectR

Re: [go-nuts] Package Stutter

2018-12-02 Thread Robert Engels
I agree that is an important consideration, but it seems less important if the packages are small and focused. I think an important point to consider is that there are systems apps, and enterprise apps. These rules seem well suited to systems apps, but maybe not so well suited to business ente

Re: [go-nuts] convert *byte to []byte

2018-12-02 Thread Ian Lance Taylor
On Sat, Dec 1, 2018 at 9:39 AM wrote: > > I am using swig wrap a c++ module , the generated go code is like this: > > type MediaFrame interface { > GetLength() uint > GetData() (*byte) > } > > I want to convert the *byte to []byte, How to do this? One approach is s := (*[1<<30]byt

Re: [go-nuts] Package Stutter

2018-12-02 Thread Ian Lance Taylor
On Sat, Dec 1, 2018 at 7:25 PM Robert Engels wrote: > > The way to fix it though it just to use dot imports, and encourage it! The > only time dot imports don’t work is when there isn’t package stutter. Seems > like a no brainer and you get the best of both worlds. Go programs that do not use d

[go-nuts] [ANN] GQ - a new library to build GraphQL servers in Go

2018-12-02 Thread staticsnow
GQ is a new library to build GraphQL servers in Go. When HouseCanary set out to build a GraphQL server to act as an API gateway to a number of existing services, we found that none of the existing libraries had quite the functionality we wanted. The biggest challenge was in scheduling batche

Re: [go-nuts] [Go2] move everything to gopath so goroot isn't required anymore

2018-12-02 Thread Gert
https://github.com/golang/go/issues/29070 On Monday, December 3, 2018 at 5:01:59 AM UTC+1, Gert wrote: > > Ok thx I will also look on the github repo if I can find it, if not I > create a new one > > On Monday, December 3, 2018 at 4:22:48 AM UTC+1, Sam Whited wrote: >> >> There has been some dis

Re: [go-nuts] [Go2] move everything to gopath so goroot isn't required anymore

2018-12-02 Thread Gert
Ok thx I will also look on the github repo if I can find it, if not I create a new one On Monday, December 3, 2018 at 4:22:48 AM UTC+1, Sam Whited wrote: > > There has been some discussion of making packages in the standard library > into modules (once that's the default versioning system) which

Re: [go-nuts] [Go2] move everything to gopath so goroot isn't required anymore

2018-12-02 Thread Sam Whited
There has been some discussion of making packages in the standard library into modules (once that's the default versioning system) which could be versioned separately from Go so that fixes could be released without having to wait on the full Go release cycle. I can't find a link at the moment, b

[go-nuts] [Go2] move everything to gopath so goroot isn't required anymore

2018-12-02 Thread Gert
Can we move stdlib (goroot) to gopath in Go2? On install you can do go get -u stdlib to download the stdlib into gopath. Basically getting rid of goroot. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop re

Re: [go-nuts] Package Stutter

2018-12-02 Thread roger peppe
> Do you really think you are losing information if this becomes: > > func matches(p Policy, a authorizer.Attributes) bool { >From my point of view, yes it makes a big difference if I see a package-qualified identifier, because I know that it's invoking some other package's abstraction. I am very

[go-nuts] [ANN] aah Go web framework v0.12.0 Released!

2018-12-02 Thread Jeevanandam M.
Website: https://aahframework.org Documentation: https://docs.aahframework.org Release notes: https://docs.aahframework.org/v0.12/release-notes.html Your feedback is very valuable. Thanks. Cheers, Jeeva -- You received this message because you are subscribed to the Google Groups "golang-nuts"

Re: [go-nuts] Package Stutter

2018-12-02 Thread 'Niko Schwarz' via golang-nuts
For what it's worth, in all this time, context.Context still looks clumsy to me and I wish you'd picked context.Ctx :) My certainty level here is high, the intensity level is low. It's like: I'm pretty sure I like the red backpack better than the black one. But the black one is fine :) Niko O

Re: [go-nuts] Package Stutter

2018-12-02 Thread Robert Engels
If can go as far as List list = sort(reverse(somelist)) I understand the import problem is not an issue when writing a package, but it’s a big issue when the use of the package is extensive, like domain types. It’s just cumbersome noise at that point, and a solution is needed IMO. > On Dec 2,

Re: [go-nuts] [ANN] Koazee a library inspired by functional programming and lazy evaluation that takes the hassle out of working with arrays

2018-12-02 Thread Iván Corrales Solera
Hey Marko, I already have benchmark for Koazee... Many changes have been done in code in order to improve the performance (At the moment being focused on improve performance for primitive types). Make comparison with other frameworks is complicated to me but I invite the owners of other simil

Re: [go-nuts] Package Stutter

2018-12-02 Thread Dan Kortschak
That's pretty different to a dot import in Go. If the imports below gave you  List list = singletonList(someobject) Then they would be comparable - the static imports are more comparable to Go's dot imports, but then in your next post you say that they're mainly used for constants, "although for