We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There might be some cases where someone would like to iterate through let’s say a solidity mapping or array.
For such reason we allow such datalake, maybe the name is not perfect.
An example of such datalake is:
IterativeDynamicLayoutDatalake( block_number=10231740, account_address="0x7b2f05ce9ae365c3dbf30657e2dc6449989e83d6", slot_index=5, initial_key=0, key_boundry=3, )
Such datalake is scoped to a specific block as it would be very weird to iterate a mapping across multiple blocks or different smart contracts.
In solidity each variable also dynamic ones such as mapping or array have their unique slot index.
To read more about storage layouts please see:
[Layout of State Variables in Storage — Solidity 0.8.24 documentation](https://docs.soliditylang.org/en/latest/internals/layout_in_storage.html)
The initial key is the initial key to be placed in the mapping, key_boundry is the key that once reached the loop will stop.
It also takes an argument increment with 1 being the default value.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
DynamicLayout Datalake
There might be some cases where someone would like to iterate through let’s say a solidity mapping or array.
For such reason we allow such datalake, maybe the name is not perfect.
An example of such datalake is:
Such datalake is scoped to a specific block as it would be very weird to iterate a mapping across multiple blocks or different smart contracts.
In solidity each variable also dynamic ones such as mapping or array have their unique slot index.
To read more about storage layouts please see:
[Layout of State Variables in Storage — Solidity 0.8.24 documentation](https://docs.soliditylang.org/en/latest/internals/layout_in_storage.html)
The initial key is the initial key to be placed in the mapping, key_boundry is the key that once reached the loop will stop.
It also takes an argument increment with 1 being the default value.
The text was updated successfully, but these errors were encountered: