Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Function selector collision is not detected with the "0" selector #1603
What's your issue about?
Vyper has an edge case in function selector collision detection. If a function with selector
Calls made to the above contract with no calldata trigger
How can it be fixed?
It seems Vyper does this -- the only edge case I've found is the "0" selector. Note, though, that Solidity does allow a function with a "0" selector along with a fallback function. It differentiates between the two by checking whether
Thanks - I think we will just reject programs with name that maps to the "0" selector