On Wed, Jun 17, 2020 at 1:09 PM jimmy frasche <soapboxcic...@gmail.com> wrote: > > This isn't a bug per se, but I can file one if requested. > > https://go2goplay.golang.org/p/AWynhg6ya7h > > Since embedding interfaces with type lists uses the intersection of > the items in the type list, it's possible to create an interface that > cannot be satisfied by any type. > > Currently this does not cause an error until you attempt to > instantiate something that uses such an interface as a bound. > > I think it would be more useful to raise the error when defining the > interface that cannot be used as it's likely an error—or at least I > can see no valid use for creating an unsatisfiable constraint.
In order to ensure that all Go compilers act the same, we would have to very carefully define the cases that are not accepted. This is a little harder than it sounds since matching is done on underlying types. At least for now I tend to think that it would be better to make this a vet check. But I don't feel all that strongly about it. 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/CAOyqgcXdxuzoJ5T7tLxso_5F%2B32KfSWrNi0N96202CQd0PiUog%40mail.gmail.com.
