Two scenarios where the definition of a function in C changes, are dynamic libraries on OSes that allow reloading the same library multiple times, or self-rewriting code.
Here you stay within the realms of a compiled language implementation, where what happens, is only expecified by compiler specific features, or OS capabilities handling executables and dynamic libraries.
Compiled code with dynamic replacement during execution,
https://learn.microsoft.com/en-us/visualstudio/debugger/hot-...
https://dev.epicgames.com/documentation/en-us/unreal-engine/...
Plain interpreters,
https://iel.ucdavis.edu/publication/2006/CUJ_proof.pdf
Just some examples.
>
Warning message
If you see the following dialog box, Hot Reload is unable to apply the current edits without restarting. You can choose either to rebuild the app and apply changes (restart) or to continue editing. If you rebuild, all application state is lost. If you continue editing, it's possible that additional changes or corrections might cause Hot Reload to work again.
[Screenshot of the apply changes dialog box]
If you select the Always rebuild when changes can't be applied option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.Also the music is way is too loud and sudden.
It's also really interesting to see the audience this is reaching. The issues on the GitHub repository are quite telling.
But if you just want to run C++ in a REPL, you can use Clang-Repl <https://clang.llvm.org/docs/ClangRepl.html> which uses the LLVM JIT to "interpret" C++.
Here, probably used ironically.
Also read up on sheafification really quick. Neither Firefox nor Chrome seem aware of it (red underline), so there.
Edit: If anyone is actually interested in interpreted C++, I think AngelScript is the most practical way for this.
As to why, I can't pretend to know the author mind, but I suspect they did it because they could, the project itself is the objective.
Funnily enough, sufficiently enough of C++ is constexpr-able that it was the driving force for compile-time reflection in C++[1], which is not unlike what the author has done.
Although the new syntax is much more readable than what the author chose to do with expression templates, it's still annoying, as is much of C++. But I still like it, so I am decidedly Stockholmed.
[1]: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p29...
stephenlf•4mo ago
phamtrongthang•4mo ago