gracenoah

In this example Interface is an interface with some methods. I really don't know what's special about it because the panic happens in this one scenario, but I've used wire.Bind...

I think you might be right. I tried to reproduce the issue again by adding back the Bind an changing the constructor to return the struct type and I couldn't....

Just got a very similar looking panic. This is the exact repro: ```go package main import "github.com/google/wire" type A struct { B string } func makeA(string) A { panic(wire.Build(wire.Struct(new(*A), "*")))...

Thanks for investigating and making a separate issue.

I'm interested in this feature. I think it wouldn't be as hard as it seems because there's already some reasonable buffer management going on. The general rule that needs to...

I think option 3 will be necessary. We care very much about how errors are constructed and reported in our code base and generally library provided panic handlers hide a...

I see one reason these tests are so flaky: they are abusing go's test parallelism. Depending on the number of cores (and therefore default test parallelism), different behaviours will happen....

I have the following config: ``` { "protoc": { "path": "/usr/bin/clang-format-6.0" } } ``` but it still gives the same error. I don't see anything in the logs.

It's actually easy to do with the existing image by just using the following docker-compose config or docker command: docker-compose: ```yaml command: ["sh", "-c", "/usr/local/bin/stellar-core --conf /stellar-core.cfg --forcescp && exec...