I know! I’m late to the Claude Code party but now I’m here, I’m all in. If you write C++ for microcontrollers, or edge inference, you already know that the rules are different from desktop software. No heap allocation after startup. No exceptions. No recursion on a 4 KB stack. And these constraints are not optional if you want your firmware to survive.
The problem is that general-purpose linters do not enforce the rules you need. Clang-tidy is powerful, but configuring it to catch you just used int instead of int32_t, requires writing custom checks in C++ against the AST. That is a significant investment for what should be a simple rule. I wanted something I could tweak for each project.
Leave a Reply