Hari
Hari
Skips appending metadata to the binary Closes https://github.com/ethereum/solidity/issues/13233
## Abstract The type-safe `ab.encodeCall(f, args)` should be extended for custom errors. ## Motivation It's very common in testing frameworks to encode custom errors (to check if a call reverts...
Take the following example:  
## Description Solidity fixes all the issues found: https://github.com/ethereum/solidity/issues/9500 Did not test it locally :( Hopefully the CI can do it? ## Checklist - [ ] tested locally - [...
Currently, the package expects a semicolon after a struct declaration, and also expects semicolons in assembly blocks. For example ```solidity struct s { uint x; } // emacs expects semicolon...
Currently, solidity doesn't allow defining errors with the following names `Panic` and `Error` (note: name, not signature). There are use cases where reverting with this error would be useful. One...
Was bought up in solidity gitter ``` library Lib { function foo(bytes32) internal pure returns (bytes32) {} function foo(bytes4) internal pure returns (bytes32) {} } ``` Compiles correctly, However ```...
There can be dirty values at the end of the bytes btw. Need to clean the last memory chunk here. Take size to be 31 and have all the memory...
https://github.com/Rari-Capital/solmate/blob/f878f20ecd6a23dd4105ee3eed7291b6311ce1fb/src/utils/MerkleProof.sol#L9 Using `calldata` is ideal here and would save a decent chunk of gas. https://github.com/Rari-Capital/solmate/blob/f878f20ecd6a23dd4105ee3eed7291b6311ce1fb/src/utils/MerkleProof.sol#L20-L36 But this means that the assembly routine would be more complex. Consider the following instead:...
```solidity contract Test {} contract Derived is Test {} function f(Test a, Test b) { a < b; a == b; a > b; a = b; } function g(Derived...