From ded96c26a382d325d7186fe5d27dd220803b30fd Mon Sep 17 00:00:00 2001 From: Nick Mudge Date: Wed, 21 Apr 2021 18:43:08 -0400 Subject: [PATCH] Automatically merged updates to draft EIP(s) 2535 (#3522) Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft, Review, or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing --- EIPS/eip-2535.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-2535.md b/EIPS/eip-2535.md index 6adb120d..9e582843 100644 --- a/EIPS/eip-2535.md +++ b/EIPS/eip-2535.md @@ -520,7 +520,7 @@ Here are some solutions to this: 1. Copy internal function code in one facet to the other facet. 1. Put common internal functions in a contract that is inherited by multiple facets. 1. Put common internal functions in a Solidity library and use the library in facets. -1. A type safe way to call an external function defined in another facet is to do this: MyOtherFacet(this).myFunction(arg1, arg2) +1. A type safe way to call an external function defined in another facet is to do this: MyOtherFacet(address(this)).myFunction(arg1, arg2) 1. A more gas-efficient way to call an external function defined in another facet is to use `delegatecall`. Here is an example of doing that: ```Solidity DiamondStorage storage ds = diamondStorage();