Missing primitives for signed calculations, and some operations for unsigned calculations

[hashedone]

There are no primitives for signed calculations in cosmwasm std, and there are not even "wrapping" operations to simulate those behavior. Not a problem for Uint128, as it can be converted to native u128, and then to i128, but it doesn't help with (de)serialization.

Also Uint256 (and probably Uint128) is missing modulo operation which is useful to have.

[webmaster128]

What's the problem/use case exactly? Are you suggesting a signed Int128 type that does string serialization in JSON and otherwise is a i128?

There are a bunch of wrapping operations in Uint128 already:

    pub fn wrapping_add(self, other: Self) -> Self {
        Self(self.0.wrapping_add(other.0))
    }

    pub fn wrapping_sub(self, other: Self) -> Self {
        Self(self.0.wrapping_sub(other.0))
    }

    pub fn wrapping_mul(self, other: Self) -> Self {
        Self(self.0.wrapping_mul(other.0))
    }

    pub fn wrapping_pow(self, other: u32) -> Self {
        Self(self.0.wrapping_pow(other))
    }

I'm sure we are missing a ton of things, but what do you need most urgently?

[uint]

Note: we should probably do #1114 before tackling this, unless there's something urgent that needs added.

[archseer]

For Uint128 operations I've been simply unwrapping the value, then re-wrapping it before serializing.

[webmaster128]

This is now tracked in #1186. cosmwasm-std 1.1 ships many of those additional implementations. Please comment there is something is still missing.

[larry0x]

If I'm not mistaken, there still isn't a primitive for signed integer. We currently use this type implemented by Margined protocol. @webmaster128 something worthwhile to be introduced into cosmwasm-std?

[webmaster128]

Right. The big question is if such a signed integer should be a tuple (unsigned value, sign) or a "proper" signed integer that encodes the sign in the two's complement. I am slightly leaning to the later as I think an Int128 should be consistent with i128 in terms of range and behaviour.

Could you create a dedicated ticket for that topic?