-
Notifications
You must be signed in to change notification settings - Fork 184
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(common,store,world): add internal table functions and use them f…
…or internal mud logic (#1513) Co-authored-by: alvrs <[email protected]>
- Loading branch information
Showing
60 changed files
with
4,108 additions
and
229 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
"@latticexyz/cli": patch | ||
"@latticexyz/common": minor | ||
"@latticexyz/store": minor | ||
"@latticexyz/world": patch | ||
--- | ||
|
||
Generated table libraries now have a set of functions prefixed with `_` that always use their own storage for read/write. | ||
This saves gas for use cases where the functionality to dynamically determine which `Store` to use for read/write is not needed, e.g. root systems in a `World`, or when using `Store` without `World`. | ||
|
||
We decided to continue to always generate a set of functions that dynamically decide which `Store` to use, so that the generated table libraries can still be imported by non-root systems. | ||
|
||
```solidity | ||
library Counter { | ||
// Dynamically determine which store to write to based on the context | ||
function set(uint32 value) internal; | ||
// Always write to own storage | ||
function _set(uint32 value) internal; | ||
// ... equivalent functions for all other Store methods | ||
} | ||
``` |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.