fix: correct per-variable bytes/string identification and remove nested scan #12603
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.
Fixed a logic error in bytes/string slot identification where the base slot value from one variable was reused while scanning all variables, which could produce false positives and imposed O(N^2) complexity. The refactor makes handle_bytes_string operate on a single variable, using that variable’s own base slot and base slot value to compute the data region, and updates identify_bytes_or_string to pass the specific storage entry and its type. This ensures correct mapping between slots and bytes/string variables and reduces complexity to O(N) across bytes/string entries while preserving existing output structure.