Implement manual border refreshing for BitString (fixes #20) #177
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 pull request implements the ability to manually control border refreshing in the
BitStringclass, addressing issue #20. Users can now choose when to refresh borders (minimum and maximum non-zero words) for performance optimization.📋 Issue Reference
Fixes #20
🚀 Key Features
Create()methods for creating BitString instances with custom border behavior🔧 Implementation Details
Core Changes
BitString.cs:
_automaticBorderRefreshingfield and propertyRefreshBordersByWord()to respect the automatic refreshing settingRefreshBorders()method that scans the entire arrayBitStringTests.cs:
Performance Benefits
When automatic border refreshing is disabled, users can:
RefreshBorders()once at the end for optimal performance✅ Testing
All tests pass successfully:
📖 Usage Examples
Default Behavior (Backward Compatible)
Manual Border Refreshing for Performance
Runtime Control
🔬 Technical Notes
RefreshBorders()method performs a complete array scan to find accurate bordersGetFirstSetBitIndex()rely on cached border values🤖 Generated with Claude Code