We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello folks,
It was such a relief when I understood that the rust eth librairie were already such matures, finding the use_contrat macro. Then I now have an abi with 2 safeTransferFrom function overrides, as defined in https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC721/IERC721.sol.
use_contrat
abi
safeTransferFrom
the name `safe_transfer_from` is defined multiple times `safe_transfer_from` must be defined only once in the type namespace of this module
No surprise here as Rust is far more strict than other common languages. But did you find a way to escape this limitation ?
Right now, i'll just edit the abi and remove manually the second function definition, but I fear I'll have to call them both one day.
one day
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello folks,
It was such a relief when I understood that the rust eth librairie were already such matures, finding the
use_contratmacro.Then I now have an
abiwith 2safeTransferFromfunction overrides, as defined in https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC721/IERC721.sol.No surprise here as Rust is far more strict than other common languages. But did you find a way to escape this limitation ?
Right now, i'll just edit the abi and remove manually the second function definition, but I fear I'll have to call them both
one day.The text was updated successfully, but these errors were encountered: