[go-nuts] golang.org/x/oauth2 bug???

2018-12-07 Thread Harald Fuchs
I think there's something fishy about clientcredentials. Having trouble with client_secrets containig special chars, first I modified clientcredentials_test.go like this: > func TestTokenRequest(t *testing.T) { > cfg := newConf("") > data := fmt.Sprintf("%s:%s", cfg.ClientID, cfg.ClientSecret) >

[go-nuts] Re: Go misfeature?

2017-10-26 Thread Harald Fuchs
Ian Lance Taylor writes: >> For us, it *did* break P1 in the sense that this silently changing its >> semantics. And how about the following? >> >> type P1 struct { >> P2 >> P3 >> } >> >> type P2 struct { >> P4 >> } >> >> type P3 struct { >> P5 >> } >> >> type P4 st

[go-nuts] Re: Go misfeature?

2017-10-25 Thread Harald Fuchs
Ian Lance Taylor writes: > On Wed, Oct 25, 2017 at 1:43 AM, Harald Fuchs > wrote: >> >> I got bitten by what I'd say is a misfeature in Go: >> >> type T1 struct { >> T2 >> T3 >> } >> >> type T2 struct { >>

[go-nuts] Go misfeature?

2017-10-25 Thread Harald Fuchs
I got bitten by what I'd say is a misfeature in Go: type T1 struct { T2 T3 } type T2 struct { T4 } type T3 struct { foo int } type T4 struct { foo int } func main() { t1 := T1{ T2{ T4{ 1, }, }, T3{ 2,