refactor: fix result.c naming to follow HACKING.md conventions#1330
refactor: fix result.c naming to follow HACKING.md conventions#1330
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 31 minutes and 20 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 (7)
✨ 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
duckdb_result_*toresult_*(rule 1)duckdb_result__*toresult__*(rule 2)get_struct_resulttorbduckdb_get_struct_result(rule 11)rbduckdb_init_duckdb_resulttorbduckdb_init_result(rule 10)duckdb.c,column.c,connection.c,prepared_statement.c,pending_result.cTest plan
🤖 Generated with Claude Code