c-next 0.2.16 → 0.2.18

package/README.md

@@ -249,6 +249,22 @@ c-next/
 
 ## Development
 
+### Toolchain Requirements
+
+C-Next has two separate toolchain contexts with different requirements:
+
+**End users** (transpiling `.cnx` files and compiling the generated C/C++ output):
+
+- Any C99-compatible compiler — GCC, Clang, IAR, `arm-none-eabi-gcc`, etc. No minimum version.
+- The generated code uses standard C99 and C++14 with no compiler-specific extensions.
+
+**Contributors** (running the test suite locally):
+
+- **GCC 9+** (or equivalent Clang) — the minimum verified to compile all generated test files
+- Verified on: GCC 9.4 (Ubuntu 20.04), GCC 11.4 (Ubuntu 22.04), GCC 12.3 (Ubuntu 22.04), GCC 13.3 (Ubuntu 24.04)
+- Ubuntu 22.04 users: `sudo apt install gcc g++` gives GCC 11, which works
+- The test suite uses `-Wall -Wextra -Werror` for `// test-no-warnings` tests, so warning behavior differences between GCC versions may surface edge cases not seen on older compilers
+
 ### Setup
 
 ```bash
@@ -258,7 +274,7 @@ cd c-next
 npm install  # Installs dependencies and Husky pre-commit hooks
 ```
 
-**Pre-commit hooks:** The project uses [Husky](https://typicode.github.io/husky/) to automatically format code (Prettier) and fix linting (ESLint) before every commit. This prevents formatting errors in PRs.
+**Pre-commit hooks:** The project uses [Husky](https://typicode.github.io/husky/) to automatically format code (Prettier) and fix linting (oxlint) before every commit. This prevents formatting errors in PRs.
 
 ### Commands
 
@@ -272,7 +288,7 @@ npm test -- tests/enum/my.test.cnx    # Run single test file
 
 # Code quality (auto-run by pre-commit hooks)
 npm run prettier:fix   # Format all code
-npm run eslint:check   # Check for lint errors
+npm run oxlint:check   # Check for lint errors
 
 # Coverage tracking
 npm run coverage:check           # Feature coverage report