Re: [go-nuts] [generics] another parsing ambiguity

Thanks, can you maybe at the complete working code snippet in your issue too ``` type R(type T) struct{} func F(type T)() { _ = func() (_ R(T)) { return R(T){} } } ``` I think it's not trivial code even after reading the issue what your solution was to the problem. -- You received this message

Re: [go-nuts] [generics] another parsing ambiguity

I've now created an issue here: https://github.com/golang/go/issues/39654. -- 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.co

Re: [go-nuts] [generics] another parsing ambiguity

At Ben did you made a github issue yet for it? Can't seem to find it https://github.com/golang/go/issues?q=is%3Aissue+cmd%2Fgo2go Thanks -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails fro

Re: [go-nuts] [generics] another parsing ambiguity

On Tue, Jun 16, 2020 at 4:49 PM Ben Kraft wrote: > > Consider the following code (playground): > > type R(type T) struct{} > func F(type T)() { > _ = func() R(T) { return R(T){} } > } > > That is, we have some parameterized type R(T), and a function literal which > returns that type R(T). (T

[go-nuts] [generics] another parsing ambiguity

Consider the following code (playground ): type R(type T) struct{} func F(type T)() { _ = func() R(T) { return R(T){} } } That is, we have some parameterized type R(T), and a function literal which returns that type R(T). (This is simplified from