Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (12)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. WalkthroughThe changes add enum end or count values and compile-time array-size checks across the core engine, GeneralsMD engine, graphics libraries, and tools. Several initialized arrays now infer their sizes, and some labels and assertion messages change. ChangesEnum and table consistency
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The PR adds compile-time table checks without introducing the identified display issues. No actionable merge blocker is established. Security Architecture ReviewSecurity architecture risk: ⚪ Minimal · up to The inspected changes strengthen compile-time consistency checks without changing existing flag values, accepted configuration names, or command-usability checks. No introduced or worsened security risk was identified. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
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 |
|
be8105b to
d22da71
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: d7c9c38e-8eca-4a77-adc2-ec210392d331
📒 Files selected for processing (12)
Core/GameEngine/Include/GameClient/ControlBar.hCore/GameEngine/Include/GameClient/Image.hCore/GameEngine/Include/GameClient/MetaEvent.hCore/GameEngine/Source/Common/INI/INIAudioEventInfo.cppCore/GameEngine/Source/GameClient/GUI/GameWindowManagerScript.cppCore/Libraries/Include/Lib/BaseFunctions.hGeneralsMD/Code/GameEngine/Include/GameClient/Shadow.hGeneralsMD/Code/GameEngine/Include/GameLogic/LocomotorSet.hGeneralsMD/Code/GameEngine/Include/GameLogic/Module/AIUpdate.hGeneralsMD/Code/GameEngine/Include/GameLogic/Module/StealthUpdate.hGeneralsMD/Code/GameEngine/Include/GameLogic/Weapon.hGeneralsMD/Code/GameEngine/Source/GameLogic/Object/ObjectCreationList.cpp
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.
d22da71 to
afa134f
Compare
…hader functions The name tables for the primary gradient and the detail color function were shorter than their W3DSHADER_*_MAX enumerations, so dumping a shader that uses bump environment luminance, modulate 2x, add signed, add signed 2x, scale 2x or mod alpha add color read past the end of the table.
Adds static_assert's for enum indexed name, lookup and function tables, so that editing an enum fails to compile until the associated array is updated. Arrays that were declared with an explicit enum count now use an unsized bound, because an explicit bound silently zero fills missing entries. Enums without a count get one. The waveTypeInfo table gets an explicit zero entry for WaveTypeStationary, which it previously got through zero fill, and the <undefined> padding of the memory category names is replaced by the assert.
afa134f to
7717c34
Compare
|
Rebased |
|
@greptileai what is your complaint? |
|
The complaint was about three behavioral changes included in the commit I reviewed—not the static assertions themselves:
Since you rebased, those findings may now be stale or already fixed. The current static-assert changes do not themselves demonstrate those defects; I should have called out the exact affected hunks instead of summarizing them as merge blockers. |
Merge with Rebase
This change fixes 2 arrays in wdump and adds static asserts for various C arrays that correspond to enum values or bit flags. This makes the code more resilient to mistakes from editing an enumeration without updating the related arrays.
AI Use
This change was 99% generated.
TODO