refactor: consolidate to single memory-efficient scanner implementation #4
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.
Summary
This PR consolidates the tokenizer to use a single memory-efficient implementation, eliminating code duplication and improving memory usage for all inputs.
Changes
streamcommand - Theencodecommand now handles all cases efficientlyNewScanner()andNewScannerOptions()to a singleNewScanner(r io.Reader, opts ...ScannerOption)following Go conventionsBreaking Changes
streamcommand (useencodeinstead - it now handles streaming efficiently)NewScannerOptionsmethod (useNewScannerwith options)Why This Change?
The previous implementation had two separate code paths:
encode: Read entire input into memory (O(n) memory complexity)stream: Used scanner with bounded memory (O(1) memory complexity)The scanner implementation is strictly superior - it handles everything the old encode did but with constant memory usage. There was no reason to maintain both implementations.
Testing
Performance
The new implementation:
🤖 Generated with Claude Code