Skip to content
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

validity checksum behavior #179

Open
SamuelCupp opened this issue Jul 24, 2023 · 0 comments
Open

validity checksum behavior #179

SamuelCupp opened this issue Jul 24, 2023 · 0 comments

Comments

@SamuelCupp
Copy link
Contributor

At the hackathon, some discussion has come up regarding the correct behavior of PreSync. As part of this, the checksum currently only runs if the variable was already valid. Should this remain the same, or should it check the variable any time it doesn't write everywhere?

It is true that checksums on variables which were previously entirely invalid is somewhat slower, any code running with this on won't be efficient anyways. It is also true that we don't have to care about the checksum in this case, but strictly enforcing the READ/WRITE declarations could still be a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant