3 ms·
Interestingly, in Ethereum smart contract languages (e.g. Solidity and Vyper), having separate types for bit vectors vs integers is common. I don't know why it
by Sniffnoy 4y ago
Interestingly, in Ethereum smart contract languages (e.g. Solidity and Vyper), having separate types for bit vectors vs integers is common. I don't know why it's caught on there but nowhere else. Obviously those languages have a pretty specialized niche and aren't really going to be used outside of that context.
- zelphirkalt 4y agoDoes this really help? Sometimes being able to treat integers as bitvectors and vice versa is something desirable. I think one needs appropriate functions, which treat integers or bitvectors as such, but not necessarily a split in types, possibly requiring any kind of type conversion.