Update GUIDELINES.md
Co-authored-by: Ernesto García <ernestognw@gmail.com>
This commit is contained in:
@ -137,7 +137,7 @@ In addition to the official Solidity Style Guide we have a number of other conve
|
||||
|
||||
* Custom error names should not be declared twice along the library to avoid duplicated identifier declarations when inheriting from multiple contracts.
|
||||
|
||||
* It is important to follow a few rules around the use of Solidity overrides to avoid introducing unintended consequences due to the interaction with multiple inheritance:
|
||||
* 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.
|
||||
|
||||
Reference in New Issue
Block a user