Please bring back the emit-c++ feature

[imaginary-person]

It'd be great if ISPC could optionally generate some C/C++ source files corresponding to the object files it generates, so that users could easily view what intrinsics they could use in their existing source code, instead of inspecting the assembly code of the generated object files. That would also make porting existing source-code easier (without making ISPC a dependency in existing projects).
Currently, ISPC makes it hard for programmers to understand how they should effectively use explicit vectorization, because having to understand assembly is quite time-intensive.

ISPC developers ought to ask themselves whether they want to see more ISPC adoption, or whether they actually want to see more applications leveraging the full potential of Intel hardware because the former is actually restricting the latter.

It seems like ISPC developers are primarily concerned about the adoption of ISPC, and less about programs leveraging the full potential of Intel hardware.

Thanks!

[imaginary-person]

Created issue #2721 for it.