bug: uint and uint256 parsed different in EIP-712 Typed Data event signatures about abitype

[greenlucid]

Isn't this intended? uint is a solidity alias, is it ABI conforming?

[krzkaczor]

@greenlucid you are right that EIP-712 doesn't support uint alias (i copied the whole selector from the sourcecode -- that's why i hit that).

However, I think that there should be some kind of error instead of a silent failure.

[tmm]

Thanks for reporting! Think we already have some code in PR that will solve this.

[Raiden1411]

@tmm not sure if the current PRs have a fix for this. Unless I am missing something on your side.

If you don't have anything I can work on a PR that fix this.

[tmm]

Based on my interpretation of this (also below):

uint, int: synonyms for uint256, int256 respectively. For computing the function selector, uint256 and int256 have to be used.

"type": "uint" and "type": "int" are both allowed. Not sure if any compilers output these as-is or convert to the fixed versions. Either way, converting things in #110

---

Separately, uint and int are already not allowed in EIP-712 Typed Data (see TypedDataType).