Compare commits

...

3 Commits

Author SHA1 Message Date
0251ffbded Update GUIDELINES.md
Co-authored-by: Ernesto García <ernestognw@gmail.com>
2023-07-04 17:47:41 -03:00
da258a58ae Update GUIDELINES.md 2023-07-03 12:32:45 -03:00
ac48658397 Add override guidelines 2023-07-03 12:05:50 -03:00

View File

@ -136,3 +136,8 @@ In addition to the official Solidity Style Guide we have a number of other conve
4. Declare the error in an extension if the error only happens in such extension or child contracts. 4. Declare the error in an extension if the error only happens in such extension or child contracts.
* Custom error names should not be declared twice along the library to avoid duplicated identifier declarations when inheriting from multiple contracts. * Custom error names should not be declared twice along the library to avoid duplicated identifier declarations when inheriting from multiple contracts.
* Solidity function overrides should follow the rules listed below in order to avoid introducing unintended consequences due to the interaction with multiple inheritance:
1. When overriding a function `foo`, always invoke `super.foo`, and pass the same arguments that were received.
2. Never use `super` outside of an override, or for a function other than the one being overridden.