Robert van Gent

Can you create your own `URLOpener`? https://github.com/google/go-cloud/blob/e6b94a04072fec4c7106c8301a56436b6fa4135d/postgres/gcppostgres/gcppostgres.go#L89 Or write the JSON to a temp file and use `GOOGLE_APPLICATION_CREDENTIALS`? I would prefer not to add custom auth mechanisms to this library...

Let's leave the feature request open to see if other people have the same request. If it's a relatively common use case I don't mind your suggestion, but if it's...

(continuing discussion from #59). I'm not sure I'm convinced that this is a good idea. It exposes a much wider API surface for `wire` with no clear use case. I...

I hear you, but IMHO it's premature to try to expose a "useful format" without knowing what the use cases are or how the data will be used. We can...

IMHO we should remove this API surface before Beta; we can always add it later if there is demand. @zombiezen @shantuo

Ah, you are right -- this bug is about changing it so that the API is public, not the other way around. Removing from Beta....

Hi @rogpeppe -- can you just add a function to do the wrapper? E.g., ``` func CloseFn(c io.Closer) func() { return func() { c.Close() } } ``` and then ```...

(reopening while we discuss)

> duplicate the signature of the function being provided and change it every time the function changes Sorry, can you clarify what you mean by that? Is it that you...

How would you expect this to work? Would you want wire to emit something like ``` go:generate wire --header_file=./path/to/header/file ``` ? That path may not exist for a subsequent call...