On Thu, Aug 13, 2020 at 3:09 PM roger peppe <rogpe...@gmail.com> wrote: > > I do feel that the "all or nothing" nature of type parameter lists (if you > specify one type parameter, you must explicitly specify all of the others > too, even if they could otherwise be inferred) is likely to get in the way > here. I'd like to see a way to specify some type parameters and not others, > so that constraint type inference can work even when, for example, there's a > generic return type parameter that can't be inferred from the arguments. We > could potentially use an underscore for that.
If I understand you correctly, we changed that when we added the constraint type inference section. See the updated https://go.googlesource.com/proposal/+/refs/heads/master/design/go2draft-type-parameters.md#type-inference section. 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/CAOyqgcVvLvuAVy%3DWVA2n4wCcpEKNfbxTN-d_K%3Dz8kz1oiK9Z3g%40mail.gmail.com.
