Don't use clang-format

This commit is contained in:
2026-07-05 19:28:26 +01:00
parent dc2fc22462
commit 26f17628a4
2 changed files with 5 additions and 34 deletions
+5 -4
View File
@@ -34,9 +34,11 @@ All code follows the patterns established in `src/wapp/`. The project prefix is
### Formatting
Machine-enforceable rules (tabs, braces, pointer alignment, continuation
alignment) are in `.clang-format` — run `clang-format -i <file>` to apply.
- **Tabs for indentation**, 8-column tab width.
- **Braces** on the same line as control statements (Attach style).
- **Pointers**: `*` against the name, not the type (`PrRhiBuffer *buf`, not `PrRhiBuffer* buf`).
- **Line width**: 120 columns.
- **Continuation lines** align to the opening parenthesis.
- **Return-type alignment**: Within each `// =====` section, align function
declaration names so the first letter of every function occupies the same
column. For pointer return types, place `*` directly against the function
@@ -47,7 +49,6 @@ alignment) are in `.clang-format` — run `clang-format -i <file>` to apply.
void prRhiDestroySwapchain(…);
PrRhiSwapchainResult prRhiAcquireNextImage(…);
```
This cannot be automated by clang-format and must be done manually.
### Storage qualifiers