Robert Griesemer

It seems confusing to have `...` stand for nothing. I would require `...` to stand for one or more zero values. So in your examples above, I'd only consider the...

I think the API here could be made relatively clean if it simply takes two types, a map of type parameters to type arguments, and then unifies for type identity....

There is a [reason](https://github.com/golang/go/issues/46477#issuecomment-852701491) why we didn't do this in the first place. ~~I don't have any principal objections to this proposal. If we accept this, I wonder whether we...

~~@neild The same reason for which type aliases were introduced in the first place, which is to make refactoring across package boundaries easier (or possible, depending on use case).~~ I...

Going through my notes I remember now why we didn't go this route in the first place: Note that an alias is just an alternative name for a type, it's...

@neild Agreed - I misread your comment as "what is the use of allowing alias types for generic types" - my bad. See my [comment](https://github.com/golang/go/issues/46477#issuecomment-852701491 ) just before your reply.

One aspect that hasn't been discussed yet is the ability to add methods to a type through aliases. Presumably, the following declarations would be valid under this proposal: ``` type...

2019-09-03 / **@bradfitz, @griesemer, @ianlancetaylor, @spf13** - #33388 **cmd/go: add build tags for 32-bit and 64-bit architectures** - **declined** (no final comments) - #32465 **net: add ability to read OOB...

**2019-10-16 / @bradfitz, @griesemer** - #34502 **net: add BufferedPipe (buffered Pipe)** - commented on new input - removed FinalCommentPeriod label - #32966 **add GOINSECURE for insecure dependencies** - **accepted 🎉**...

I think @bcmills makes some good points. I am also in favor of simply adding ```Go func (x *Int) Float64() (float64, Accuracy) ```