1. The tool illuminates compiler‑generated code
Users appreciate being able to see what the compiler actually does—especially for lambdas, templates, and synthesized functions.
- “This is what let me understand lambdas. Great tool.” — IshKebab
- “Definitely trying this out. I've always had the problem of ‘but what is the compiler thinking?’ with C++ in particular.” — jsrcout
- “Ooo I love these things. I wrote a C++ → Clang → JS transpiler so I could show value change states on top of the C++ source code …” — alankarmisra
2. C++ feels overly complex, making such a tool feel necessary
Several commenters express sadness or frustration that the language itself is not obvious enough to read without extra help.
- “I must be the only one … feel a little strange, somewhere between sad, angry, annoyed and disappointed … that a language needs (or at least is of good use) such a tool.” — f1shy
- “I wish what is the first interpretation of my code to be obvious. … How did we end with such a complex language?” — f1shy
- “I wish the readme example showed a lambda capture. Now that's where compiler magic REALLY shows up.” — StilesCrisis
3. It’s mainly an educational aid; similar hidden transformations exist in other languages and become intuitive with practice
Others argue the tool isn’t a sign of a broken language but a useful learning resource.
- “No a language doesn’t need it. It’s an educational tool for those new to the language … With practice language features just become automatic …” — kccqzy
- “I don't think it's only C++ though, Python decorators, Rust macros, almost every language's compiler write code you never see. C++ just does more of it and makes it harder to guess.” — rs545837
- “In what language is compiling simple? … Lisp is simple to compile. Even C … also basic, and maybe other 100 languages …” — f1shy (counterpoint to the complexity claim)