[go-nuts] Re: Discussion on "Vendoring edge case, critical problem"

Nope, vendoring remains unsuitable for library authors. On Sunday, 19 June 2016 15:14:57 UTC+10, Tyler Compton wrote: > > A user brought up a problem with the current vendoring setup regarding > exposing types of a vendored dependency. There was a lot of great > discussion and it seemed like

[go-nuts] Discussion on "Vendoring edge case, critical problem"

A user brought up a problem with the current vendoring setup regarding exposing types of a vendored dependency. There was a lot of great discussion and it seemed like there was a consensus that something needed to change, but I don't see that anything had come of it. Here is the discussion:

[go-nuts] Re: WebAssembly as a target

I would be very interested in this. I think GopherJS has shown how compelling it can be to be able to write Go that can run in the browser. It serves as a great preview of that ability, enabling one to experiment and prototype things. But to really get the best performance, minimum file size,

Re: [go-nuts] Re: [ANN] primegen.go: Sieve of Atkin prime number generator

On Saturday, June 18, 2016 at 12:21:21 AM UTC+2, gordo...@gmail.com wrote: On Friday, June 17, 2016 at 4:48:06 PM UTC+2, gordo...@gmail.com wrote: > > I am not on a high end Intel CPU now, but when I was I found that with a > > buffer size adjusted to the L1 cache size (8192 32-bit words or 32

[go-nuts] Re: benchmarking not working (always) go1.7beta

thanks, i was guessing something like that, these are very short pieces of linear code. so i did try; using returned values, repeating the test 10x in the loop, and adding stop/start. the code's on github, (https://github.com/splace/signals) but this is a selective test, so its really

[go-nuts] Re: benchmarking not working (always) go1.7beta

Without seeing the code (hint, hint) I'm guessing that your benchmark got optimised away. Here are some links with suggestions on how to make your benchmark reliable. http://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go#compiler-optimisation

Re: [go-nuts] Powersets and append() confusion

2016-06-18 19:16 GMT+02:00 Oliver Schmid : > Hi. I made a string only version of the powerset function on Rosetta Code > and ran into a bug where a slice input to append() [one, two, three, four] > seems to be replaced by [one, two, three, five]. What. Note that append()

[go-nuts] Powersets and append() confusion

Hi. I made a string only version of the powerset function on Rosetta Code and ran into a bug where a slice input to *append()* [one, two, three, four] seems to be replaced by [one, two, three, five]. What. Here's the bug on the Go Playground

[go-nuts] generating interfaces from proto3 (grpc)

Hi I've a proto3 file: == message Any { } message InsertParams { Any Record = 1; } service myService { rpc Insert (InsertParams) returns (InsertResponse); } where I have an "Insert" API which expects a InsertParams struct as the parameter. However, the InsertParams

Re: [go-nuts] Re: [ANN] primegen.go: Sieve of Atkin prime number generator

On Saturday, June 18, 2016 at 12:21:21 AM UTC+2, gordo...@gmail.com wrote: > > On Friday, June 17, 2016 at 4:48:06 PM UTC+2, gordo...@gmail.com wrote: > > > I am not on a high end Intel CPU now, but when I was I found that with > a buffer size adjusted to the L1 cache size (8192 32-bit words or

Re: [go-nuts] Re: go1.7beta2 prints "too many values in struct initializer" when I ran "go test" for gopkg.in/vmihailenco/msgpack.v2

2016-06-18 11:42 GMT+09:00 Dave Cheney : > This could be caused by setting GOROOT to a value that does not match the > `go` binary in your path. If you have another version of Go installed, > please remove it, unset GOROOT, and follow the installation instructions on > the Go