memcheck - clarify vector access #1664
Open
+405
−99
Conversation
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
jeremylt
force-pushed
the
jeremy/memcheck-tidy
branch
from
cebe980
to
dbc5943
Compare
jeremylt
commented
Sep 16, 2024
jeremylt
force-pushed
the
jeremy/memcheck-tidy
branch
2 times, most recently
from
260f1a3
to
bdb8f9d
Compare
jeremylt
force-pushed
the
jeremy/memcheck-tidy
branch
from
bdb8f9d
to
7e5ca22
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tidies up the internals of the Memcheck CeedVector impl, making it clearer how we check access assumptions.
I then mirrored those changes into the QFunctionContext impl and threw in a bit of tidying for the QFunction too.