-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Bytes hooks #151
Bytes hooks #151
Conversation
a20b0be
to
25839cc
Compare
cat $(UKM_CONTRACTS_TESTING_INPUT_DIR)/bytes_hooks.rs >> [email protected] | ||
echo ">)>" >> [email protected] | ||
|
||
# echo "<(<" > [email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I plan to uncomment this as soon as we can parse ukm.rs.
<ukm-bytes-buffers> | ||
M => M[NextId <- b""] | ||
</ukm-bytes-buffers> | ||
<ukm-bytes-next-id> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@virgil-serbanuta , Are we treating the bytes using a pseudo indexed-memory approach? Is that the purpose of <ukm-bytes-next-id>
and <ukm-bytes-buffers>
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so. This is a mapping from indexes to Bytes objects, with indexes generated sequentially from the <ukm-bytes-next-id>
cell. It is sort of similar with a heap in which memory is never freed, and which holds only values of type Bytes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the explanation, Virgil.
Relevant for #135