Repository navigation
Keep SemLock OS calls behind SemHandle methods - #8740
Conversation
Stop exporting libc semaphore pointers from host_env. Stdlib now waits, posts, and reads values through SemHandle instead of *mut sem_t / HANDLE. Assisted-by: Grok:4.6
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: RustPython/RustPython/.coderabbit.yml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe change moves semaphore operations behind platform-specific ChangesSemaphore handle encapsulation
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Refactor Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
libcsemaphore pointers fromhost_env.stdlibwaits, posts, and reads values throughSemHandleinstead of*mut sem_t/HANDLE.Follow-up to #8739.
Test plan
cargo check -p rustpython-host_envcargo check -p rustpython-stdlibSummary by CodeRabbit