WHITELIST-LENGTH with "dynamic" size #295
Open
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
ensure that if runtime checks are enabled, the current number is valided on use, not the maximum
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.
ensure that if runtime checks are enabled, the current number is valided on use, not the maximum
Note: this may lead to several index out of bound messages, if
WHITELIST-LENGTHis not setup correctly (initial / incremented before used) - so consider to not pull that or do so after verifying that it does work"dynamic" as likely known this construct uses the maximum definition size = reserved space on first use, only the access is dynamic (at least it should, if not then there's a bug in GC, so double check before pull :-)