refactor: fix memory_helper.c naming to follow HACKING.md conventions#1327
refactor: fix memory_helper.c naming to follow HACKING.md conventions#1327
Conversation
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 10 minutes and 19 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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
memory_helper.cfromrbduckdb_memory_helper_*tomemory_helper_s_*to follow HACKING.md rule 8: singleton methods must use theclassname_s_methodnamepatternrbduckdb_prefix is reserved for extern functions (rule 11); using it on static functions was a naming convention violationTest plan
🤖 Generated with Claude Code