Conversation
Probably easiest to reference this: klauspost/stdgozstd#1 The decoder still accepts both.
📝 WalkthroughWalkthroughThe change adds initialization of the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can disable sequence diagrams in the walkthrough.Disable the |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@zstd/encoder_options.go`:
- Line 45: The empty-frame fast path currently forces Checksum: false even
though fullZero (default true) and crc default may indicate checksums should be
emitted; update the empty branch in EncodeAll (the branch around the empty input
in encoder.go) to propagate the encoder option for crc/checksum instead of
hard-coding false — i.e., read the encoder's checksum/crc option (the same
setting controlled by fullZero/crc) and set Checksum accordingly when
constructing the empty frame response so the advertised checksum behavior
matches non-empty paths.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 9d96f758-617a-431d-a265-7aa57c35a8d9
📒 Files selected for processing (1)
zstd/encoder_options.go
Probably easiest to reference this: klauspost/stdgozstd#1
The decoder still accepts both.
Summary by CodeRabbit