Skip to content

Commit

Permalink
EIP-2535: Made clear facets do not have to be reusable (#5730)
Browse files Browse the repository at this point in the history
* EIP2535: Fixed misspelling, tweaked wording

* EIP2535: Updated dependencies

* added space

* EIP2535: Make clear that facets do not have to be reusable
  • Loading branch information
mudgen authored Sep 29, 2022
1 parent 90cc92d commit 552e3dc
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion EIPS/eip-2535.md
Original file line number Diff line number Diff line change
Expand Up @@ -377,7 +377,7 @@ require(success, "myFunction failed");
```
6. Instead of calling an external function defined in another facet you can instead create an internal function version of the external function. Add the internal version of the function to the facet that needs to use it.

### Facets are Reusable and Composable
### Facets can be Reusable and Composable

A deployed facet can be used by any number of diamonds.

Expand All @@ -387,6 +387,8 @@ It is possible to create and deploy a set of facets that are reused by different

The ability to use the same deployed facets for many diamonds reduces deployment costs.

Facets can also be designed for a specific diamond and not be reusable in other diamonds.

A function signature is the name of a function and its parameter types. Example function signature: `myfunction(uint256)`. A limitation is that two external functions with the same function signature can’t be added to the same diamond at the same time because a diamond, or any contract, cannot have two external functions with the same function signature.

All the functions of a facet do not have to be added to a diamond. Some functions in a facet can be added to a diamond while other functions in the facet are not added to the diamond.
Expand Down

0 comments on commit 552e3dc

Please sign in to comment.