Doesn't flattening and using a service like gopkg.in solve this issue? Then
you can have both flat structure and multiple versions of the same library
since different versions of the same library appear as different packages
since the import path is different.
On Thursday, April 13, 2017 at
Oh well, probably never mind, forgot to call the sorting function at one
place, so that is likely the reason...
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
> Performing separate stable sorts on a partial key does not produce a
stable sort on the full key.
I think that it does, when you sort from the last key to the first key.
When I want to sort the slice by (Gateway, Channel, Device),
then sorting by Device, then Channel, then Gateway using a
Hi,
I have a slice of points:
type Point strcut {
Gateway string
Channel int
Devce int
}
Now I execute
cc := make([]Point, 0)
// Fill cc with points (skipped here).
sort.SliceStable(cc, func(i, j int) bool {
return cc[i].Device < cc[j].Device
})
sort.SliceStable(cc, func(i,
Hi,
I am running go test on a set of packages. Some of these packages do
contain tests and some don't.
The packages that *don't* contain any test files import a Kafka package
that links librdkafka and uses Cgo.
When I run go test with this set of packages I end up getting
# pkg-config --cflags
Hmm, that sucks for my use case, but at least I know now that it's a
feature.
Cheers,
Ondřej
On st 13. 9. 2017 19:25 Ian Lance Taylor <i...@golang.org> wrote:
> On Wed, Sep 13, 2017 at 9:06 AM, Ondřej Kupka <ondra@gmail.com> wrote:
> >
> > I am running go test
