Initialization order fix#62
Conversation
…isable base nodes limit for debug mode, rank/file offsets
Reduce the number of elements taken from bucket3 from 5 to 1.
Reduce the limits for bucket2 and bucket3 sizes in optimization.
Replaced random device initialization with a fixed seed for reproducibility in tests.
yeah... the logs showed that the attacks testcase took the longest:(
downgrading requirements somehow.... yeah it always fails due to TLE
Add assertions to Rank and File operator overloads for Direction.
Adjust the size limit for bucket2 based on platform to improve performance on Windows runners.
Refactor size determination for bucket2 and bucket3 based on platform.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (15)
🔥 Files not summarized due to errors (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR refactors the chesslib engine's core Position API from camelCase to snake_case naming, introduces explicit repetition-hash tracking, restructures castling metadata storage, modernizes attack generation to support runtime compilation, and updates all dependent code to use the new APIs. ChangesCore Engine API & State Architecture
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related issues
Possibly related PRs
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
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 |
No description provided.