Closed darrenlangley closed 5 years ago
This lack of clarity has come up a few times over the past week. I believe we should probably support uint
vs int
explicitly.
I was thinking about that but was holding off creating an issue while waiting for a first draft of the spec in https://github.com/ethereum/eth2.0-specs so that we could discussed it there.
Hi all,
I noticed that ssz (https://github.com/ethereum/beacon_chain/blob/master/ssz/ssz.py) treats the type intX more like a uint rather than an int.
This works fine when signed int usually go between -128 to 128:
Also this errors with overflow:
If this is expected than cool, although it is a bit confusing calling it int rather than uint.