Contracts Draft: unsatisfiable contracts

[Qais Patankar]

For unsatisfiable contracts like the one mentioned just above this, 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

[alan...@gmail.com]

I suspect they won't want to make this a compiler error because of other possible conflicts that may arise when one contract is embedded within another.

A vet warning should be feasible though.

Alan

[Ian Lance Taylor]

On Tue, Jul 30, 2019 at 7:04 AM <alan...@gmail.com> wrote:
>
> I suspect they won't want to make this a compiler error because of other possible conflicts that may arise when one contract is embedded within another.
>
> A vet warning should be feasible though.

I agree.

Ian