Ok, maybe I'm a bit off topic. But this also points out why I firmly 
believe that libraries should not add things to the default flag set in an 
init function. This is just one of many cases where that can cause 
problems. 

@Library developers - please, please consider supplying the user with an 
function they can *optionally *call *if* they want to use your flags. 

My 2ยข.

Jake

On Tuesday, January 30, 2018 at 8:51:58 AM UTC-5, Marcin Owsiany wrote:
>
> I admit I'm somewhat new to Golang, how do I solve this problem?
> My program uses two libraries, both of which have github.com/golang/glog 
> in their /vendor/ directories.
> This results in a panic at runtime, apparently because two copies of glog 
> try to initialize the same flag on initialization.
>
> Marcin
>

-- 
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 golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to