[go-nuts] Monkey patching question
An upstream package object is lowercase and thus unexported and thwarts my attempt at using bouk/monkey (github.com/bouk/monkey). How should I insert a fmt.Println in one of its methods? Thank you. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/878siuuwbm.fsf%40dick.
Re: [go-nuts] rpc.debugLog unexported
Thanks for your reply. Do you regularly edit standard libs as described (and then presumably edit them back)? I copied /usr/lib/go-1.13/net/rpc to my project directory, then changed all imports of "net/rpc" to "./net/rpc", and then set debugLog (in my shadow copy, not /usr/lib/go-1.13). It got the job done but still felt wrong. > Ian Lance Taylor writes: > On Sat, Dec 7, 2019 at 9:12 AM wrote: >> >> How can I turn on debugging in net/rpc/server.go? >> >> There is a promising variable called `debugLog` in there. How should I >> toggle it? > I don't know how much it will help, but the way to toggle it is to literally > edit net/rpc/debug.go to set debugLog to true. There's no mechanism for > setting it dynamically. > Ian -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/87muc2g07z.fsf%40dick.
[go-nuts] rpc.debugLog unexported
How can I turn on debugging in net/rpc/server.go? There is a promising variable called `debugLog` in there. How should I toggle it? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/87a7849nb8.fsf%40dick.