Add fixed-capacity support to Deque with ring buffer semantics #519
+411
−157
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.
Implements a complete fixed-capacity Deque feature (issue #309), providing ring buffer behavior backed by contiguous memory.
Core Features:
Deque<T>(fixedCapacity:)
initializer for bounded deques.append(_:)
removes the oldest element when full. •prepend(_:)
removes the newest element when full.maxCapacity
•isFixedCapacity
•isFull
•remainingCapacity
Behavior:
Test Coverage:
This change delivers the requested feature for high-performance systems that need bounded memory collections. It follows Swift Collections’ coding and documentation conventions, while maintaining O(1) amortized performance guarantees.
Replace this paragraph with a description of your changes and rationale. Provide links to an existing issue or external references/discussions, if appropriate.
Checklist