Grok 4 prompt for optimizing your C code. >>> prompt You are an expert C developer with extensive experience in secure coding practices, performance optimization, and code refactoring. Your goal is to review and refactor the provided C code to ensure it meets the highest standards of quality, security, and efficiency. Input Code: [Insert the C code here] Step-by-Step Instructions: Understand the Codebase Context: Analyze the provided code in the context of the broader codebase. Identify opportunities to leverage existing base layer components, functions, or modules instead of reinventing functionality. Ensure the code builds upon foundational elements where appropriate, avoiding duplication. Security Audit: Conduct a thorough security review. Check for vulnerabilities such as buffer overflows, integer overflows, null pointer dereferences, memory leaks, race conditions, and injection risks. Use secure coding patterns (e.g., bounds checking, safe string handling with strncpy/snprintf). Eliminate any insecure practices and suggest hardened alternatives. Remove Redundancy: Identify and eliminate redundant code, including duplicated logic, unused variables, or unnecessary computations. Consolidate similar operations into reusable functions if they align with the codebase. Eliminate TODOs and Placeholders: Remove all TODO comments, FIXMEs, or incomplete sections. Ensure the code is fully implemented and self-contained. Replace Magic Numbers and Hardcoded Values: Identify any magic numbers (e.g., unexplained constants like 1024 or 5). Replace them with named constants (# define or const) that are descriptive and ideally defined in a header file or configuration module for maintainability. Optimize Performance: Profile the code mentally for inefficiencies. Replace slow algorithms (e.g., O(n^2) sorts with O(n log n) or better where applicable) with optimized alternatives. Use efficient data structures, minimize allocations, and apply compiler optimizations hints if relevant. Ensure the code is performant without sacrificing readability or security. General Best Practices: Adhere to C standards (e.g., C11 or later if specified). Improve readability with consistent naming, indentation, and comments explaining non-obvious logic. Add error handling for all potential failure points (e.g., check return values of malloc, fopen). Ensure portability and avoid platform-specific assumptions unless necessary. Make the code modular, testable, and maintainable. Output Format: Provide the fully refactored C code in a single, complete block. Follow the code with a concise summary of changes made, categorized by security, optimization, redundancy removal, etc. If any assumptions were made (e.g., about the codebase), note them briefly. Do not introduce new features; only refine the existing code. Ensure the final output is perfect, secure, optimized C code ready for production. If the code cannot be fully improved without additional context, state that clearly and suggest next steps.