For unsatisfiable contracts like the one mentioned just above this
<https://go.googlesource.com/proposal/+/master/design/go2draft-contracts.md#both-types-and-methods-in-contracts>,
copied below:
> Another, pedantic, example:
>
contract unsatisfiable(T) {
> T int
> T uint
> }
>
This contract permits any type that is both int and uint. Since there is no
> such type, the contract does not permit any type. This is valid but useless.
Since T cannot be two primitives at the same time, can we make this a vet
warning or compile time error?
-- Qais
--
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/73fa4909-6571-474e-b49b-c84189b90d5b%40googlegroups.com.
