Test native and wasm C kernels

[anutosh491]

A release, 0.8.0 was made to make the C kernels available on conda-forge/emscripten-forge. Check #393

But these kernels lack any sort of testing. We should have some before the next release.

[mcbarton]

The first issue which needs to be resolved to allow the python kernel tests to run for the c kernel, is to have following dependent on whether your using the C or C++ kernel. You will get an assert error about the language info not matching otherwise

xeus-cpp/src/xinterpreter.cpp

Line 315 in c7628c6

result["language_info"]["name"] = "C++";

[JohanMabille]

Indeed, we can deduce the languages from the arguments passed to the interpreter (where we have -std=C++XX or -std=cXX depending on the kernelspec, see https://github.com/compiler-research/xeus-cpp/blob/main/share/jupyter/kernels/xcpp20/kernel.json.in#L7-L13 for instance). It might not be the most robust solution, but we don't really have a mean to read the kernelspec from the kernel itself in the xeus stack.

[mcbarton]

Indeed, we can deduce the languages from the arguments passed to the interpreter (where we have -std=C++XX or -std=cXX depending on the kernelspec, see https://github.com/compiler-research/xeus-cpp/blob/main/share/jupyter/kernels/xcpp20/kernel.json.in#L7-L13 for instance). I might not be the most robust solution, but we don't really have a mean to read the kernelspec from the kernel itself in the xeus stack.

This method is something I had already began trying out since I wrote the comment above. My first attempt ended in failure (inspired by this PR #349 that tried to get the c++ standard that way), but I think it shouldn't be too difficult to implement.

[vgvassilev]

We could add an interface in CppInterOp that gives us that information.

[JohanMabille]

That would be definitely better