Summary of Changes

Hello @waruqi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on applying a comprehensive code formatting standard across the codebase, driven by an updated .clang-format configuration. The changes aim to enhance code consistency, readability, and maintainability, making it easier for developers to navigate and contribute to the project. It touches a wide range of C source files, ensuring a uniform style throughout the core modules.

Highlights

• Clang-Format Configuration Update: The .clang-format file has been extensively updated to enforce a consistent coding style. Key changes include setting BasedOnStyle: LLVM, explicitly defining indentation with 4 spaces, attaching braces (BreakBeforeBraces: Attach), and adjusting various alignment, spacing, line breaking, and penalty settings to improve code readability and maintainability.
• Code Formatting Across Core Modules: Numerous C source files across base64, bloom_filter, curses, engine, fwatcher, hash, io, libc, os, package, process, readline, sandbox, semver, string, thread, tty, and winos modules have been reformatted. This includes consistent spacing around macro definitions, standardizing function signatures (e.g., lua_State* lua to lua_State *lua), placing opening braces on the same line for conditional blocks, and consistent pointer casting. Trailing blank lines in header files have also been removed.
• Improved Macro Readability: Multi-line macro definitions in core/src/xmake/curses/curses.c have been refactored to use \ for line continuation and align braces, enhancing their readability and adherence to the new formatting rules.
• Windows-Specific Code Page Handling: In core/src/xmake/winos/ansi.c, the xm_expand_cp function now correctly handles CP_OEMCP and CP_ACP for expanding code page values, ensuring proper character encoding management on Windows.