I imagine developers as experienced as the creators of this evaluated the C options and decided C++ was in fact not more of a detriment than a gain.
It has its problems but blindly being anti C++ is silly.
It has its problems but blindly being anti C++ is silly.
It's been a C codebase so far. Introducing C++ makes this no longer the case. This has strong implications for both development and deployment. I'm perplexed since there exist battle-tested code generation engines written in C (e.g. dynasm). Correct me if I'm wrong but it doesn't look like asmjit is anything special in that regard.
I can't imagine Joe Armstrong being happy about this.
I do agree with you though.
https://github.com/erlang/otp/pull/2745#issuecomment-6914821...