[acover]

> Both plans have value, but they have different priorities and therefore choose different constraints… most of all, they either embrace up-front the design constraint of perfect C++ interop and ecosystem compatibility, or they forgo it (forever; as I argue in the talk, it can never be achieved retroactively, except by starting over, because it’s a fundamental up-front constraint).

> cppfront is on the TypeScript plan:

> full seamless interop compatibility with ISO Standard C++ code and libraries without any wrapping/thunking/marshaling,

> full ecosystem compatibility with all of today’s C++ compilers, IDEs, build systems, and tooling, and

> full standards evolution support with ISO C++, including not creating incompatible features (e.g., a different concepts feature than C++20’s, a different modules system than C++20’s) and bringing all major new pieces to today’s ISO C++ evolution as also incremental proposals for today’s C++.