Closed kingoflolz closed 6 years ago
As far as I can tell, they don't do Int because Parity has no need for it, since it's not needed to evaluate EVM code. AFAIK, this package mostly exists for assembly x86 optimizations
@jtremback seems like int exist in the EVM http://solidity.readthedocs.io/en/v0.4.21/types.html#integers, but maybe they do not need to use it because of 2's complement arithmetic? As long as there is no need for handling overflow or displaying the numbers, int256 and uint256 should be equivalent
@tomusdrw new changes pushed
@tomusdrw sorry just realized I didn't ping you when I pushed my latest changes, anyways let me know if there is anything else you would like me to change. Also curious what is the relation of the uint crate in this repo with this https://github.com/paritytech/bigint/ Thanks!
@debris ping
Any progress on this @tomusdrw ?
specifically:
Into<type>
(no need to manually .into())Note this breaks backward compatibility because doing
uint + <some number type>.into()
is ambiguous, but I will be happy to make the upstream PRs to fix this as requiredAlso, I wonder if you know if there is an Int type somewhere by parity