decoder: intentional unconditional allocation in large-array branch for TrackOutputBytes correctness#26
Closed
Copilot wants to merge 2 commits into
Closed
decoder: intentional unconditional allocation in large-array branch for TrackOutputBytes correctness#26Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
… limits Add a MaxOutputBytes field to DecodeOptions that tracks cumulative decoded output size across a single decode operation. Before each allocation (array element, union arm, optional field, opaque data), the size is added to a running total; if it exceeds MaxOutputBytes the decode is aborted with ErrOutputBytesExceeded. Key changes: - Add TrackOutputBytes method and TrackOutputBytesOf[T] generic helper - Cap array pre-allocation at 256 elements, growing via append beyond that - Track allocations in DecodeFixedOpaque, decodeArray, decodeUnion, decodeMap, and allocPtrIfNil - Bump minimum Go version to 1.25 for generics support Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2 tasks
Copilot
AI
changed the title
[WIP] Address feedback on MaxOutputBytes decode option implementation
decoder: intentional unconditional allocation in large-array branch for TrackOutputBytes correctness
Mar 11, 2026
112f917 to
c677e1b
Compare
|
Closing — improvements from this PR have been incorporated into #22 where applicable. Thank you! |
This file contains hidden or 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
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.
A reviewer suggested reusing a caller-provided slice's backing array in the large-array decode path to avoid unnecessary allocations. This PR addresses that feedback by confirming the unconditional
reflect.MakeSliceallocation is intentional and correct.Why the current implementation is correct
TrackOutputBytesis called per-element as the slice grows. Reusing an existing slice's backing array would silently bypass tracking for the pre-allocated capacity, creating an accounting gap in cumulative output-size limit enforcement.MaxOutputBytesfeature also allocated unconditionally viareflect.MakeSlice; this preserves that contract.Reusing
v's existing backing array (whenv.Cap() >= maxPrealloc) would skipTrackOutputBytesfor those pre-existing bytes, defeating the limit enforcement.💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.