Fuse key normalization and hashing #313
Merged
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.
Replace normalizeKey+fastKeyHash call pairs with a single normalizeKeyAndHash path in parser key creation/lookup flows.
For untransformed bare and single-quoted keys, compute key hash directly from source bytes while still materializing String for storage. Keep existing String-based hash path for transformed keys and double-quoted escape-decoded keys.
This removes repeated key re-hashing work in parseKeyValue/createKey* and fillTablePath hot paths without changing behavior.