Anton Bukov

@yaronvel no, you should support addresses **shorter** than 20 bytes, because it could contain first zero bytes for the probability reasons. Encoders could encode addresses as numbers and use for...

+1 for CocoaPods support!

I agree that `toEthSignedMessageHash` and `toTypedDataHash` functions are probably the most efficient implementations written in Solidity Assembly, btw we are using the same in @1inch: https://github.com/1inch/solidity-utils/blob/95bc66ff4267ae112f97b8296c2515a6dd999449/contracts/libraries/ECDSA.sol#L260-L282

@frangio what do you think?

@Amxx please check out the PR, I believe it is good improvement because it can bring more granular support to this feature.

We used this guardian in one of ERC20 extensions, it’s obvious not a good idea to use singleton guardian for multiple different extensions, so using separate struct makes a lot...

You can achieve the same functionality by the following code: ```solidity bytes memory data = abi.encode(addressArray); clone = IMPLEMENTATION.clone(data); ``` And on the implementation side: ```solidity function _getAddressArray() private pure...

Libraries and their structures can not be inherited and ovveriden, but composition can be used. It is implicit, but still very powerful and I think compiler can inline all those...

Having libs for most of the functionalities would allow next gen of utility to the library. ERC20Lib library logic could be used multiple times inside one contract, for example to...

I see that composition currently allows only static hierarchies. We can’t have agile method to compose: ERC20, Votes and Delegates for example. The thing which can help with dynamic composition...